On Fri, 11 Mar 2011 17:01:46 +0100 Lennart Poettering <lenn...@poettering.net> wrote:
> On Fri, 11.03.11 08:49, Mike Kazantsev (mk.frag...@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... > Probably my changes entirely, I have the aforementioned format defined in the configuration. My apologies, should've mentioned that to avoid confusion. > Lennart > -- Mike Kazantsev // fraggod.net
signature.asc
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
