> -----Original Message----- > From: Andrey Borzenkov [mailto:arvidj...@mail.ru] > Sent: Friday, March 11, 2011 11:01 AM > To: Rainer Gerhards > Cc: Michael Biebl; Mike Kazantsev; systemd-devel@lists.freedesktop.org > Subject: Re: [systemd-devel] systemd-logger and external syslog daemon
> Actually looking at kernel printk implementation, it is pretty robust > and will just pass unknown severity through. Which means that > prefixing them with e.g. <s> will mark lines as belonging to systemd > and allow further filtering and post-processing. This sounds like a good solution to me. I could easily parse that off and know what's going on. Along these lines, we may include a timestamp for those messages as well (or rely on the overall printk setting, which sounds a bit more natural to me...). I am not a kernel hacker, so I may need to get some help setting up a test environment for this to try out... Rainer _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
