https://bugzilla.novell.com/show_bug.cgi?id=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c24 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|kasievers@novell.com | --- Comment #24 from Kay Sievers <kasievers@novell.com> 2011-03-22 16:35:28 UTC --- (In reply to comment #23)
(In reply to comment #22)
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?
Because early boot is mostly hardware system/subsystem init, and messages from early boot tools _should_ mix with the kernel messages during that time to be reliably sorted and kernel time-stamped. Today there are lots of kernel components managed from userspace, and they should share the same log buffer during early bootup. Also on embedded-like systems the kernel ring-buffer connected to /dev/log is all what you ever want for "syslog".
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?
Yeah, it sounds like it. Not sure what's the problem with syslog-ng here. The systemd bridge maybe needs to be stopped when syslog runs. But as said, I don't know the details, only that rsyslog seems to work fine.
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
Maybe it's syslog-ng itself that calls klogd somehow? It might be, that this problem can not be solved properly for syslog-ng without using native service files and socket activation. Proper socket passing needs native service files and does not work with compat sysv services. Syslog is special regarding compat handling, because systemd itself dependends on a specific behavior. -- 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.