On Thu, Apr 05, 2001 at 11:31:19AM -0400, Brian E. Seppanen wrote:
You may try to use klogd, and use that to direct kernel logs to syslog-ng.
There's no way for me to say this without sounding like a complete idiot, but I thought klogd needed to be running to direct messages to /proc/kmesg, which syslog-ng would then read? If this isn't the case then for all I know I've been creating contention for that file by having both syslog-ng reading from it as well as having klogd running. There may be no trouble with syslog-ng other than my ignorance. I've stopped klogd and I'll see if I still get kernel messages, thankfully it won't take long as we usually see a bad ICMP packet or two during the day which the kernel logs.
Ops, that may cause a race condition. Both klogd and syslog-ng tries to read kmsg, and if klogd wins, syslog-ng stays blocked. I don't know why the fd is not in non-blocking mode though. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1