[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning

[bugzilla at redhat.com]

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 #31 from Rainer Gerhards <rgerhards at hq.adiscon.com>  2009-06-15 02:04:04 EDT ---
> 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.

You almost seem to intentionally misunderstand me. Look at the code, or do a

*.* /path/to/file

in your rsyslog.conf and you will see that rsyslog *does* log these messages.
But no point in further arguing this...

I made a test with stderr. I changed rsyslogd so that it keeps fd 2 open after
a fork. Then I did 

/sbin/service rsyslog start

Nothing showed up on the terminal. Just to make sure, I added an

fprintf(stderr, "rsyslogd start\n");

right as the first line of main(). Again, I did a

/sbin/service rsyslog start

And again, nothing showed up at the controlling terminal. My conclusion is that
/sbin/service does suppress the daemon's stderr. Am I wrong here? What kind of
magic do I need to do to make stderr appear?

-- 
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.