On Fri, 15 Jan 2010, Michael Biebl wrote:
2010/1/15 Michael Biebl <[email protected]>:
2010/1/15 Philip M. Gollucci <[email protected]>:
Michael Biebl wrote:
=====
:programname, contains, "NetworkManager" /var/log/NetworkManager.log
~
:programname, contains, "wpa_supplicant" /var/log/NetworkManager.log
~
=====
1) rsyslogd always pukes on itself if the config file doesn't parse.
not new.
2) Its documented that selectors syntax is not a stable API / config
file syntax, though, the maintainer should have noted it in UPDATING.
I would have hit this tomorrow myself.
You forgot the part, where I said that I remove those lines and
rsyslog still doesn't log anything.
And the fact that if it fails to parse, it should complain loudly and
not fail silently.
unfortunantly in my experiance it doesn't complain loudly :-(
in V5 there is a new option to tell it to exit if it can't read the
config.
I suspect that the actual config error is significantly earlier in the
config. One thing that I frequently tripped over when switching back and
forth was th HUPisRestart option. In V5 that's not a valid option anymore
and needs to be removed.
can you post your full config?
David Lang
Anyway, let's see what Rainer has to say.
Michael
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
