Rainer Gerhards wrote: >> >> I think config parsing problems should be output unconditionally to >> stdout; but what do I know :-) Anyway, relying on the logging >> service to tell you about a problem with the logging service seems >> - umm - over-confident. > > Well, that's the meat of it. So what shall I do? I am asking this > question for roughly 20 months now, and so far obviously did not get > a good answer, nor do I have one. As I wrote, we can already output > error messages to stderr. Would it really help to add another option > to send them to stdout as well?
It outputs to stderr? I don't seem to be able to make it do that (as far as I know, both stderr and stdout should be going to the console). With the config file containing the invalid action line, I tried this: # rsyslogd -c4 -N1 rsyslogd: version 4.5.6, config validation run (level 1), master config /etc/rsyslog.conf rsyslogd: End of config validation run. Bye. Shouldn't it at least THEN have told me there was something wrong with the conf? I would expect anything that tells me it's a "config validation run" to output any errors in the config to the same channel that message gets printed on. > > All suggestions on how to handle error notifications are *very* > welcome. > Output to stderr would be fine with me; but I'm not convinced it does that. -- Jack. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
