Feature changed by: Dr. Werner Fink (WernerFink) Feature #312466, revision 4 Title: Separate user and kernel log messages openSUSE Distribution: New Priority Requester: Important Requested by: Andreas Jaeger (a_jaeger) Product Manager: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Partner organization: openSUSE.org Description: SUSE used blogd to separate kernel and user log messages during boot. With systemd now everything is written to the kernel ring buffer. We should separate those again. Relations: - syslog (novell/bugzilla/id: 696963) https://bugzilla.novell.com/show_bug.cgi?id=696963 Discussion: #1: Kay Sievers (kay_sievers) (2011-05-31 15:13:14) They are separated by the facility value in the syslog prefix. The kernel was changed to handle this separation just fine. This is actually feature not something to work around. Proper syslog implementations can separate the messages just fine. Early boot tools should use the same log target as the kernel. Today, there is no reason to distinguish kernel- from userspace during early boot. As soon as the real syslog is running, the kernel buffer is not used anymore. + #2: Dr. Werner Fink (wernerfink) (2011-05-31 16:18:11) (reply to #1) + # echo Test printk > /dev/kmsg ; sleep 1; tail /var/log/messages | grep + printk May 31 16:06:16 shannon kernel: [1743439.436249] Test printk + ... linux/drivers/char/mem.c ... kmsg_write() ... linux/kernel/printk.c + ... DEFAULT_MESSAGE_LOGLEVEL 4 /* KERN_WARNING */ ... + linux/include/linux/kernel.h ... KERN_WARNING -- openSUSE Feature: https://features.opensuse.org/312466