[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning
bugzilla at redhat.com
bugzilla at redhat.com
Mon Jun 15 06:18:13 UTC 2009
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=136141
--- Comment #33 from Rainer Gerhards <rgerhards at hq.adiscon.com> 2009-06-15 02:18:13 EDT ---
Yes, I made a mistake. Looks like /sbin/service does not prevent stderr from
showing up ;)
Find a fix for the recent v3-stable here:
http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=ff6232d2bee06fbbc25ad83a1cf3bb798884679a
It keeps stdout and stderr open across fork(). Thus, error messages can be seen
at wherever they point to. I would still suggest to *log* the emitted error
messages, if any, via a rule, because you obviously will not see these error
messages during an automated system startup.
Note that there is also an additional small cleanup fix in git (or remove the
fprintf(stder, ...) after main() yourself.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the fedora-triage-list
mailing list