https://bugzilla.novell.com/show_bug.cgi?id=696963
https://bugzilla.novell.com/show_bug.cgi?id=696963#c1
--- Comment #1 from Kay Sievers 2011-05-30 13:12:38 UTC ---
Please just install the upstream-maintained native systemd service files
named after the syslog implementation, and drop the multiplexing of all
possible syslog implementations through the magic SUSE sysconfig script on
systemd boots.
We need proper and unified native management of services, and which
implementation of syslog should be started is to be configured by:
systemctrl enable/disable, and not by magic multiplex switches in SUSE
config files, which we should avoid in the future for many reasons.
Syslog is special regarding SYSV compatibility. The current version of
systemd requires socket passing to be active for syslog to integrate with
systemd's only syslog logic, and will only work with native service files
and not with SYSV compat scripts.
Systemd also does not support any klogd-like process listening for kernel
messages and forwarding them to /dev/log. It will create a message loop
with the systemd's own kmsg bridge. The syslog implementation needs to
support reading kernel messages directly, to integrate properly with
systemd, or needs to explicitly work around such issues.
--
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.
