https://bugzilla.novell.com/show_bug.cgi?id=656104 https://bugzilla.novell.com/show_bug.cgi?id=656104#c0 Summary: syslog daemon -- socket activation / systemd integration Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: mt@novell.com ReportedBy: mt@novell.com QAContact: qa@suse.de CC: radmanic@novell.com, werner@novell.com, pczanik@genesi-usa.com, kasievers@novell.com Found By: --- Blocker: --- Implement systemd socket activation for all 3 syslog daemons we support: syslog-ng, syslogd and rsyslogd[¹].
From http://lists.opensuse.org/opensuse-factory/2010-11/msg00566.html: [...] syslog is very special in that context, like udev or D-Bus are special for systemd.
Systemd needs to race-free pass over its own /dev/log socket that connects to the kernel buffer, hence the requirement for syslog. With that infrastructure, you can even replace any running syslog, even with a different product, any time, without ever losing a single message. But it needs to support systemd's socket activation. Most other stuff is just a normal service. [...] I'm setting the Severity to critical, because implementing it makes it possible to replace the syslog daemon without to loose messages. [¹] Patches for rsyslogd implementing socket activation are available, as referenced by Kay: http://lists.opensuse.org/opensuse-factory/2010-11/msg00564.html http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=41327992680cfb8dd602ea9... http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=8e51241a50531dc10d00e54... It should be quite straight forward to implement this for the another syslog daemons as well. See also feature request: #310327: use systemd session manager instead of SysVinit/upstart -- 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.