I reported this at https://bugs.launchpad.net/ubuntu/+source/system-tools-backends/+bug/298777: If I try to stop system-tools-backends after it was already stopped, I get an error. For example, if I run "sudo invoke-rc.d system-tools-backends" twice, I get: chr1s@chris-desktop:~$ sudo invoke-rc.d system-tools-backends stop * Stopping System Tools Backends system-tools-backends [ OK ] chr1s@chris-desktop:~$ sudo invoke-rc.d system-tools-backends stop * Stopping System Tools Backends system-tools-backends start-stop-daemon: warning: failed to kill 7993: No such process [ OK ] This is because when I closed system-tools-backends the first time, it left a stale PID file in /var/run. Manually deleting /var/run/system-tools-backends.pid prevented the init script from failing again.
Created attachment 20453 [details] [review] cleanup-pid-file.patch Here is the patch applied in Ubuntu. This applied to version 2.6.0 of system-tools-backends
The original problem might have been caused by http://bugs.freedesktop.org/show_bug.cgi?id=19604 as the PID file was created without an explicit file mode.
Pushed as 52b2419d4ad8641c3dd63272f6c1ca97f570bf45. Thanks!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.