debian/cubicweb-ctl.cubicweb.init
author Alexandre Fayolle <alexandre.fayolle@logilab.fr>
Mon, 14 Dec 2009 14:57:10 +0100
branchstable
changeset 4113 986fc01be83c
parent 3001 74e842e4871a
child 6803 691dac4c6a05
permissions -rw-r--r--
TIMESTAMP column type has a special meaning for SQLServer, avoid using it for that driver (with help from logilab.common.adbh)

#!/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)
        /usr/bin/cubicweb-ctl reload --force
        ;;
    status)
        /usr/bin/cubicweb-ctl status
        ;;
    *)
        /usr/bin/cubicweb-ctl $1 --force
        ;;
esac