https://bugzilla.novell.com/show_bug.cgi?id=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c29 --- Comment #29 from Dr. Werner Fink <werner@novell.com> 2011-03-22 17:55:13 UTC --- Yes this can be done with native systemd service files as well as with old init scripts as well. The only problem for the old system v init or better startproc(8)/chekproc(8) is to distinguish an exit status with success from a crashed daemon its selfs later on. I guess that if syslog-ng crashes even with systemd we may run into this loop ... is this correct? Or does systemd ignore syslog messages after syslog-ng has activated the socket but crashed anyway? AFAIK this should not happen after sd_notify(0, "READY=1"), shouldn't it? Is there a way to use e.g. sd_booted() for klogd as well as for syslog-ng or syslogd and wait on the OK from systemd -- 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.