https://bugzilla.novell.com/show_bug.cgi?id=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c34 --- Comment #34 from Kay Sievers <kasievers@novell.com> 2011-03-22 20:45:20 UTC --- (In reply to comment #32)
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.
They all need to get native service files. There is no way around it in the long run.
I didn't tested it until now and also not with syslogd yet, but it seems that the external klogd makes the difference.
Yeah, *looks* like the issue.
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).
It has had a timeout in the 11.4 release. The recent version does not stop itself anymore, it runs forever. We don't really support systemd on 11.4, development happens in Factory. We will probably just update the 11.4 systemd version when the stuff has stabilized with the upcoming Fedora release. -- 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.