https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c6
--- Comment #6 from Kay Sievers
(In reply to comment #2)
Most enterprise users want to have the choice between all three sysloggers and the openSUSE is the base of all enterprise products.
Sure, if the syslog implementation supports systemd, it can be enabled/disabled with systemctl commands. No magic needed here, it will work just fine, like everything else on the system.
Next is that systemd should not abuse the kernel kprintf logging buffer but use its own logging ring buffer.
"Abuse' is your personal opinion, which the systemd developers don't share. We have quite to opposite feedback on this feature from many people involved in this decision. Early-boot messages are mixed with the kernel messages, in 'dmesg' and that's exactly what you want to look at if things go wrong. These days it does not matter at all if boot/init components run in user- or kernel-space, hence they should log to the same target during early boot, until a real syslog is available. Laptop- and embedded-like setups do not need to run any syslog service at all, but they still have a fully working 'syslog' from the kernel. It's just that nothing is ever written to disk. Rsyslog can distinguish the userspace messages from the kernel messages just fine, and can even write them to different log files. -- 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.