https://bugzilla.novell.com/show_bug.cgi?id=671525
https://bugzilla.novell.com/show_bug.cgi?id=671525#c33
--- Comment #33 from Kay Sievers
All syslog daemons are currently using socket activation -- just without syslog.service file.
That was a bug in an earlier systemd version. Socket activation is only available for natively started services, not for sysv compat services.
[Service] ExecStopPost=/bin/systemctl start systemd-kmsg-syslogd.service
It never needs to be started, systemd takes care of it, if syslog goes away and no syslog service startup transaction is pending.
ExecStart=/etc/init.d/syslog start
Never use any sysv init scripts in systemd service files. It will just deadlock. Thei stuff is really not meant to be used that way. We should stick to the upstream way of integrating this.
Do we need some another dependencies, ...?
We need native service files for all syslog implementations with the real name of the package, and leave the multiplexed sysv "syslog" script behind us. Enabling or disabling will be managed by systemd symlinks not by sysconfig magic. -- 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.