On Tue, Jun 26, 2007 at 05:56:23PM +0200, Balazs Scheidler wrote:
When in place, syslog-ng seems to perform fine - it seemed to pick up all facilities and levels per initial testing. However, the machine then promptly hung. Or, rather, I found that all susefirewall packet messages (kernel, SFW2)) started going to console, in addition to file. I don't have any console destinations per se since these are headless, so I don't know exactly why messages would go to console when they should be going through /proc/kmsg (and thus syslog-ng), correct?
set the kernel's console log level. this is done by klogd but not syslog-ng automatically.
something like "dmesg -n4" should help.
Now documented in the FAQ: http://www.campin.net/syslog-ng/faq.html#klogd -- Nate Yea, tho I walk thru the valley of the shadow of clues, I shall fear no luser, for Thou lart with me, Thy chicken and Thy manual, they comfort me.