[syslog-ng] re:kernel message logging

Bruce M. Penrod bmpenrod at endruntechnologies.com
Mon Aug 14 20:06:49 CEST 2006

Balazs Scheidler wrote:

>On Fri, 2006-08-11 at 16:11 -0700, Bruce Penrod wrote:

>> As a workaround, I tried using klogd with syslog-ng.  I did turn off the 
>> syslog-ng source for /proc/kmsg.  Now I don't see kernel messages on my 
>> console, but I don't get any kernel message logging either.  Again, 
>> should this work?  I don't see that there should be any special source 
>> definition in syslog-ng.conf for this to work.

> In addition to Sandor's response, I'd like to add that this combination
> should work, however klogd uses its own syslog() implementation instead
> of using the one in libc, and it does not support
> unix-stream() /dev/log, only unix-dgram(). That's probably the reason
> why it does not work.Thanks to both Sandor and Balazs for the answers to my kernel logging questions.

I did not know about /proc/sys/kernel/printk, or that dmesg had the capability
to set it, just like klogd.  Learn something new all the time.

I was using the unix-stream source for /dev/log.  Might be good to explain the
need to use the datagram source for klogd in the reference docs, although I
don't see why anyone would want to use it now.  I only tried it because of the
console logging issue, which Sandor's suggestion has solved nicely.

Thanks for the quick responses.


More information about the syslog-ng mailing list