I have for a long time been annoyed about services that start and then fail, outside of the grasp of the init scripts. That will make the init-scripts think that the service is still running, meaning that I have to execute two commands to get it back to work when the problem is fixed. First I have to zap it: /etc/init.d/service zap And then start it up again. /etc/init.d/service start Running /etc/init.d/service restart won't work, because the system thinks that the service is running, looks for it, and reports an error when it can't be found. That is of course correct, but the elegance is still missing. That's why I wrote the "zapstart" function. It is in fact very basic. A small change to /sbin/runscript.sh adds "zapstart", which will zap a program and then start it up normally. A great time-saver for me Reproducible: Always Steps to Reproduce: 1. 2. 3.
"/etc/init.d/service zap start" should already do what you want.
yep, no need to patch to save you from typing 1 more character
Oh. What a fool I am. Thanks!
