https://bugzilla.novell.com/show_bug.cgi?id=732912 https://bugzilla.novell.com/show_bug.cgi?id=732912#c17 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #17 from Dr. Werner Fink <werner@suse.com> 2011-11-30 17:01:27 UTC --- .. reading leads to the point 12 In the daemon process, write the daemon PID (as returned by getpid()) to a PID file, for example /var/run/foobar.pid (for a hypothetical daemon "foobar"), to ensure that the daemon cannot be started more than once. This must be implemented in race-free fashion so that the PID file is only updated when at the same time it is verified that the PID previously stored in the PID file no longer exists or belongs to a foreign process. Commonly some kind of file locking is employed to implement this logic. .. IMHO it is race free as sendmail creates its pids only if all is OK (configuration, network, ..) and running. It is upto systemd to handle this, e.g. by a timeout or similar or will systemd upstream really will cause sendmail and other daemons to be rewritten due the new systemd isn't able to handle timeouts in a clear way? -- 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.