I have several java-based services that someone wanted to run as daemons. I would have preferred running them in Tomcat, but they didn't want to administer that. So I thought I would create an init script in /etc/init.d, and use that to stop/start the service and to check its status via service --status-all. If you follow the documentation on this the Debian people recommend using their init functions in /lib/lsb/init-functions. The ones I don't like are start-stop-daemon and the use of pid files in /var/run. Firstly, for a java service run as java -jar MyProg.jar ...options... &
this doesn't fit into the mould of an executable daemon with arguments, since the program name is just "java" and the actual "daemon" is a long path name with even longer classpath variables etc. Also I don't see the point of the pid file. Its only purpose is to test if the daemon is running. But you can do that with:
PID=`ps aux | grep $DAEMON | grep -v grep | awk '{print $2}'`
That gives you the process ID so long as you have a long enough name for the daemon. So if $PID
is empty the daemon is not running, and according to the standard I am supposed to call exit 3
or exit 0
if it was running. However service --status-all
ignores this return code. Oh yes. After hours of hacking I found a script that did work because it called log_success_msg
in each of the two cases (see below). And with that, it works. Presumably because this reads the script status code. Without those lines service --status-all
reports that the service "isn't running" no matter what.
In the following sample code just replace my daemon, and all the paths etc with yours. The meat of the script is generic, although it doesn't support reload.