https://bugzilla.novell.com/show_bug.cgi?id=671525
https://bugzilla.novell.com/show_bug.cgi?id=671525#c23
Dr. Werner Fink
Systemd has it's own /dev/log early-syslog-bridge implementation. Any userspace program can just use glibc's syslog() during very early bootup and will write to the kernel log buffer. As soon as the real syslog starts, it takes over the open /dev/log fd from systemd for new messages and reads the kernel log buffer.
In other words: systemd encroachs on the kernel message ring buffer by redirecting the user space messages from /dev/log to /dev/kmsg? Why does systemd not use its _own_ ring buffer? Beside this the klogd is started _after_ syslog-ng or syslogd using openlog() and syslog(). At this point /dev/log should belong to syslog-ng or syslogd, shouldn't it? The klogd executed in once mode does not use openlog() nor syslog() and is used in /etc/init.d/boot.klog to write out /var/log/boot.msg -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.