Package: systemd Version: 215-5+b1 Followup-For: Bug #770090 Hello, maybe this sheds some light on the issue: it seems that syslogd gets KILLed at some point and then automatically starts a new instance:
[...] Nov 21 18:24:29 dotcom systemd[793]: Stopped target Timers. Nov 21 18:24:29 dotcom systemd[793]: Stopping Sockets. Nov 21 18:24:29 dotcom systemd[793]: Stopped target Sockets. Nov 21 18:24:29 dotcom systemd[793]: Starting Shutdown. Nov 21 18:24:29 dotcom systemd[793]: Reached target Shutdown. Nov 21 18:24:29 dotcom systemd[793]: Starting Exit the Session... Nov 21 18:24:29 dotcom systemd[793]: Received SIGRTMIN+24 from PID 1938 (kill). Nov 21 18:24:33 dotcom rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="675" x-info="http://www.rsyslog.com";] exiting on signa l 15. Nov 21 18:25:03 dotcom rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="671" x-info="http://www.rsyslog.com";] start Nov 21 18:25:03 dotcom systemd-modules-load[154]: Inserted module 'dm_crypt' Nov 21 18:25:03 dotcom systemd-modules-load[154]: Inserted module 'loop' Nov 21 18:25:03 dotcom systemd-fsck[150]: /dev/sda1: clean, 251653/1954560 files, 5240880/7864320 blocks Nov 21 18:25:03 dotcom systemd-modules-load[154]: Inserted module 'lp' Nov 21 18:25:03 dotcom systemd-modules-load[154]: Inserted module 'ppdev' Nov 21 18:25:03 dotcom systemd-modules-load[154]: Inserted module 'parport_pc' [...] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
