[systemd-devel] systemd-logger and external syslog daemon
kay.sievers at vrfy.org
Fri Mar 11 09:06:11 PST 2011
On Fri, Mar 11, 2011 at 17:47, Rainer Gerhards <rgerhards at hq.adiscon.com> wrote:
>> From: Andrey Borzenkov [mailto:arvidjaar at mail.ru]
>> Well ... the problem really is that format is supposed to be single
>> character, which does not really support bit operations and such. What
>> attached (completely untested) path - which adds <u> marker to anything
>> written into /dev/kmsg?
> If it is just a single character, I need to obtain the real facility/severity
> somewhere. Could that be written to some fixed place, e.g. immediately after
> "<u>"? That way, I'd know exactly what is going on and can remove the extra
> formatting on the syslogd side.
Let's just check if we can fix the kernel to support the full 8 bit,
and fill-in the LOG_USER when /dev/kmsg is used, if no other facility
is passed-in. That way the both messages are easily distinguished
without any breakage of the format.
More information about the systemd-devel