https://bugzilla.novell.com/show_bug.cgi?id=849387 https://bugzilla.novell.com/show_bug.cgi?id=849387#c3 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |systemd-maintainers@suse.de InfoProvider|fcrozat@suse.com | --- Comment #3 from Frederic Crozat <fcrozat@suse.com> 2013-12-11 12:58:24 UTC --- for "forking" service (like nfs), systemd tried to track one of the PID as the "main" PID. Usually, it is best handled when a PIDFile exists (and systemd is notified of this pidfile, using PIDFile: in the LSB header) otherwise, systemd will pick "one" PID and uses it as "main" PID. If it disappear, systemd will stop the service. The "best" way to handle this would be to replace the nfs initscript in several service for each daemon started. In the mean time, try adding in the LSB header: # X-Systemd-RemainAfterExit: true This will prevent systemd to "stop" the service if the main (guessed) PID is terminated. Of course, if you have a way to specify the real PID to track, use it instead. -- 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.