author | Sylvain Thénault <sylvain.thenault@logilab.fr> |
Thu, 12 Dec 2013 12:28:43 +0100 | |
changeset 9358 | 1e0235478403 |
parent 7788 | cc8670be7b2e |
child 10235 | 684215aca046 |
permissions | -rw-r--r-- |
#!/bin/sh -e ### BEGIN INIT INFO # Provides: cubicweb # Required-Start: $remote_fs $syslog $local_fs $network # Required-Stop: $remote_fs $syslog $local_fs $network # Should-Start: postgresql pyro-nsd # Should-Stop: postgresql pyro-nsd # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start cubicweb application at boot time ### END INIT INFO # FIXME Seems to be inadequate here # FIXME If related to pyro, try instead: # export PYRO_STORAGE="/tmp" cd /tmp # FIXME Work-around about the following lintian error # E: cubicweb-ctl: init.d-script-does-not-implement-required-option /etc/init.d/cubicweb start # # Check if we are sure to not want the start-stop-daemon machinery here # Refer to Debian Policy Manual section 9.3.2 (Writing the scripts) for details. case $1 in force-reload) python -W ignore /usr/bin/cubicweb-ctl reload --force ;; status) python -W ignore /usr/bin/cubicweb-ctl status ;; start|stop|restart|*) python -W ignore /usr/bin/cubicweb-ctl $1 --force ;; esac