http://bugzilla.suse.com/show_bug.cgi?id=1118068
http://bugzilla.suse.com/show_bug.cgi?id=1118068#c3
--- Comment #3 from Konstantin Voinov
Created attachment 791575 [details] /etc/systemd/system/syslogd.service
For SLES-15 and Tumbleweed this already fixed a long time
@@ -18,23 +18,19 @@ Description=System Logging Service Conflicts=syslog-ng.service rsyslog.service Requires=var-run.mount -Requires=syslog.target +Requires=syslog.socket Requires=network.target Requires=klogd.service -Before=syslog.target Before=klogd.service -After=var-run.mount -After=network.target
you might test out the attached service unit file, which *after* current syslog service has been stopped with systemctl, should be used as /etc/systemd/system/syslogd.service by daemon-reload, activation, and start.
Does this work for you?
Attached .service runs syslogd without auto-backgrounding (-n key). That does not work on 42.3. systemctl doesn't exits after starting: ExecStart=/usr/sbin/syslogd -n $ADDITIONAL_SOCKET So, now my syslog.service look like this: [Unit] Description=System Logging Service Conflicts=syslog-ng.service rsyslog.service Requires=var-run.mount Requires=syslog.socket Requires=network.target Requires=klogd.service Before=klogd.service [Service] Type=notify Sockets=syslog.socket StandardOutput=null Environment=ADDITIONAL_SOCKET= ExecStartPre=/usr/sbin/syslogd-service-prepare EnvironmentFile=-/var/run/syslogd/additional-log-sockets.env ExecStart=/usr/sbin/syslogd $ADDITIONAL_SOCKET ExecReload=/bin/systemctl kill --signal=TSTP klogd.service ExecReload=/sbin/killproc -p /var/run/syslogd.pid -HUP /usr/sbin/syslogd ExecReload=/bin/systemctl kill --signal=CONT klogd.service ExecReload=/bin/systemctl kill --signal=USR2 klogd.service [Install] WantedBy=multi-user.target Alias=syslog.service -- You are receiving this mail because: You are on the CC list for the bug.