https://bugzilla.novell.com/show_bug.cgi?id=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c22 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|kasievers@novell.com | --- Comment #22 from Kay Sievers <kasievers@novell.com> 2011-03-22 15:07:58 UTC --- (In reply to comment #21)
Kay: We have 3 syslog daemons and one klogd feeding all three.
klogd seems not to run when rsyslog is used, at least not with the same problem. syslog-ng seems to cause the loop, syslog I don't know.
Why systemd does not support other syslog implementations? I do not see any technical reason for this.
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. Klogd feeds the kernels log buffer to /dev/log I guess, and creates a loop that way, reading it's own messages again. There is nothing really in systemd that is non-supporting, but without knowing the details, the thing klogs does doesn't seem to fit into that.
Beside this there is already the possiblity not to use the klogd as rsyslogd is also able to use its own klog module.
That seems to be the case. And systemd systems recommend the use of rsyslog because it is properly integrated from rsyslog upstream. When people switch from syslog-ng to rsyslog, all seems to work, without knowing what really makes the difference between the both, the daemon itself, the configuration, or the init script logic. The long-term plan is to get rid of the init script and have native service files shipped with the upstream syslog tarball, instead of the current magic. Klogd is not in that picture. -- 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.