2010/1/15 <[email protected]>: > On Fri, 15 Jan 2010, Michael Biebl wrote: > >> 2010/1/15 <[email protected]>: >>> >>> you may also try adding '$AboortOnUncleanConfig yes' to the config. I >>> found that gave me an error in some cases where it just wouldn't do what I >>> expected without it. >> >> Oh, the irony :-) >> >> rsyslogd: Option value must be on or off, but is 'yes' >> rsyslogd: the last error occured in /etc/rsyslog.conf, line >> 11:"$AbortOnUncleanConfig yes" >> rsyslogd: CONFIG ERROR: could not interpret master config file >> '/etc/rsyslog.conf'. [try http://www.rsyslog.com/e/2124 ] >> >> >> Unfortunately, no further clues. Will try the undocument-everything >> approach now. > > anything different if you use 'on' instead of 'yes'?
Tried that of course. There is no relevant error message. Further testing revealed: -d no longer gives me the debug messages on stdout. I had to run kill -USR1 $(cat /var/run/rsyslogd.pid) to get a verbose output. With a tiny rsyslog.conf like $ModLoad imuxsock *.* /var/log/debug-rsyslog I finally get log messages again. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
