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.
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 tools-backends [ OK ] desktop: ~$ sudo invoke-rc.d system- tools-backends stop tools-backends start-stop-daemon: warning: failed to kill 7993: No such process
[ OK ]
* Stopping System Tools Backends system-
chr1s@chris-
* Stopping System Tools Backends system-
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.