https://bugzilla.novell.com/show_bug.cgi?id=671525
https://bugzilla.novell.com/show_bug.cgi?id=671525#c31
--- Comment #31 from Marius Tomaschewski
(In reply to comment #21)
Kay: We have 3 syslog daemons and one klogd feeding all three.
klogd seems not to run when rsyslog is used, at least not with the same problem.
rsyslog provides a klogd as module -- /etc/rsyslog.conf: $ModLoad imklog.so # kernel logging (may be also provided by /sbin/klogd), # see also http://www.rsyslog.com/doc-imklog.html. $klogConsoleLogLevel 1 # set log level 1 (same as in /etc/sysconfig/syslog). In syslogd case, the external /sbin/klogd is started. syslog-ng is also able /proc/kmsg itself, but traditionally we start /sbin/klogd here as well. (In reply to comment #30)
We need socket activation for proper race-free fd hand-over, which can only be done with native service files.
All syslog daemons are currently using socket activation -- just without syslog.service file.
Here is rsyslog's upstream systemd service file which kills the bridge: http://git.adiscon.com/?p=rsyslog.git;a=blob;f=rsyslog.service.in;hb=HEAD
OK, this means we just need to provide a syslog.service file killing the bridge -- something like this: [Unit] Description=System Logging Service [Service] Type=forking ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service ExecStopPost=/bin/systemctl start systemd-kmsg-syslogd.service ExecStart=/etc/init.d/syslog start ExecReload=/etc/init.d/syslog reload ExecStop=/etc/init.d/syslog stop Sockets=syslog.socket [Install] WantedBy=multi-user.target Do we need some another dependencies, ...? -- 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.