[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning
bugzilla at redhat.com
bugzilla at redhat.com
Sun Jun 14 16:42:04 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 #30 from Michael Schwendt <mschwendt at gmail.com> 2009-06-14 12:42:03 EDT ---
What else can I do to avoid that we don't talk past eachother, please?
> rsyslog does not discard selectors silently. First of all, it logs them,
It does _not_ log them. At least not in the example I offer in this ticket.
Yes, it's bad luck that an entire rule gets disabled, see comment 14, please.
> It does not make sense to include a facility to output
> to stderr if nobody will ever see stderr.
What sort of messages do you refer to?
If I log in to a machine and run "sudo /sbin/service rsyslog restart", why
would I not see warnings/errors printed to stderr?
--
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