[systemd-devel] systemd-logger and external syslog daemon

Lennart Poettering lennart at poettering.net
Fri Mar 11 08:01:46 PST 2011


On Fri, 11.03.11 08:49, Mike Kazantsev (mk.fraggod at gmail.com) wrote:

> > Hmm, that is borked. We do provider proper error levels when we write
> > things to kmsg. This must get lost later on. But we do strip the
> > facility, so that it gets replaced by "kernel", that is true.
> > 
> > The only reason we strip the facility however is because the "dmesg"
> > tool chokes on it. The kernel is completely fine with it. I think if
> > we'd fix dmesg we should have no trouble with making the kernel log
> > buffer a full featured syslog queue like any other.
> > 
> > And the "kernel[-]: " syntax must be from your log implementation,
> > too. What syslog implementation is that?
> > 
> 
> The same rsyslog.
> Format is "facility.priority cmd[pid]: ", but in case of kmsg looks like
> rsyslog doesn't try to interpret "process[pid]: " prefix, at least, so
> my guess is that it doesn't try to get any syslog metadata from this
> messages, just passing them as-is from kernel.warning kernel[-].

Hmm, the log messages look different for us. Probably different default
configuration on Fedora and your distro...

Lennart

-- 
Lennart Poettering - Red Hat, Inc.


More information about the systemd-devel mailing list