On Fri, 11.03.11 19:41, Andrey Borzenkov (arvidj...@mail.ru) wrote: > Well ... the problem really is that format is supposed to be single > printable character, which does not really support bit operations and > such. What about attached (completely untested) path - which adds <u> > marker to anything written into /dev/kmsg?
Please don't do this. Let's not invent new interfaces here. Let's just stick to traditional syslog which is perfectly capable of handling this, because it allows for a full 8bit number between < and > which is 3 bits priority plus 5 bits facility. Then, let's fix the kernel side of kmsg to implicitly add in LOG_USER as facility for everything coming in from /dev/kmsg that has has facility=0 set. Basically what Kay suggested. Facilities might not be the most powerful idea ever invented, but they are useful to distuingish kernel from userspace messages, as there is LOG_KERNEL for the former and all other facilities for the latter. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel