debian/cubicweb-ctl.cubicweb.init
author Sylvain Thénault <sylvain.thenault@logilab.fr>
Wed, 19 Jan 2011 18:01:28 +0100
branchstable
changeset 6850 2b9e58174327
parent 6803 691dac4c6a05
child 6917 e080e7465ac4
permissions -rw-r--r--
[repo] move cursor creation into the try/except, it may raises an InterfaceError if the connection is closed

#!/bin/sh -e

### BEGIN INIT INFO
# Provides:          cubicweb
# Required-Start:    $syslog $local_fs $network
# Required-Stop:     $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
        ;;
    *)
        python -W ignore /usr/bin/cubicweb-ctl $1 --force
        ;;
esac