https://bugzilla.novell.com/show_bug.cgi?id=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c32 --- Comment #32 from Marius Tomaschewski <mt@novell.com> 2011-03-22 20:37:20 UTC --- (In reply to comment #26)
It might not be worth investigating how the current syslog init magic and syslog-ng fails, and we better just go directly for native systemd service files, and make them working in a way systemd expects them to work.
We have to investigate. It is IMO not an option to drop syslog-ng/syslogd. The socket activation in all 3 syslog daemons on 11.4 is basically same. I didn't tested it until now and also not with syslogd yet, but it seems that the external klogd makes the difference. In case of rsyslog (via syslog.service alias init script), systemd seems to detect it and stops systemd-kmsg-syslogd.service (it is stopped on my fresh 11.4 installation here without any changes). -- 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.