https://bugzilla.novell.com/show_bug.cgi?id=791076 https://bugzilla.novell.com/show_bug.cgi?id=791076#c3 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |mt@suse.com, | |werner@suse.com InfoProvider|werner@suse.com | --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2012-11-26 13:05:04 UTC --- The generator does nothing magic, it simply generates the core for the unit /lib/systemd/system/syslog.service: [Service] Type=forking PIDFile=/var/run/rsyslogd.pid Sockets=syslog.socket StandardOutput=null ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service ExecStartPre=-/var/run/rsyslog/addsockets ExecReload=/bin/kill -HUP $MAINPID ExecStart=/sbin/rsyslogd -c 7 -f /etc/rsyslog.conf ExecReload=/sbin/killproc -p /var/run/rsyslogd.pid -HUP /sbin/rsyslogd I've no idea where the bad exit status comes from as rsyslog seems to run. Maybe the rsyslog status not always that clear for systemd even with Type=forking? -- 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.