init_template.sh revision 616c706887911c1ebb4816428f8e64f74add79a3
#
# VirtualBox generic init script.
#
# Copyright (C) 2012 Oracle Corporation
#
# This file is part of VirtualBox Open Source Edition (OSE), as
# available from http://www.virtualbox.org. This file is free software;
# General Public License (GPL) as published by the Free Software
# Foundation, in version 2 as it comes in the "COPYING" file of the
# VirtualBox OSE distribution. VirtualBox OSE is distributed in the
# hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
#
### BEGIN INIT INFO
# Required-Start: $local_fs
# Should-Start: $syslog
# Required-Stop: $local_fs
# Should-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: %DESCRIPTION%
### END INIT INFO
## @todo We should really replace the daemon starting, stopping and checking
# code with a tool of our own written in C, which we could always use
# instead of the LSB functions.
cr="
"
tab=" "
IFS=" ${cr}${tab}"
'unset' -f unalias
'unalias' -a
unset -f command
## A generic service script which can be used, after substituting some place-
# holders with service-specific values, to run most services on LSB, System V
# or BSD-compatible service management systems. As we control both the service
# code and the init script we try to push as much as possible of the logic into
# the service and out of the very system-dependent service configuration
# scripts and files. See the help text of the "install_service.sh" helper
# script for more details.
#
# Furthermore, to simplify deployment, we will install all init scripts using
# this generic template manually during the post install phase or at run time
# using LSB functions if they are available (as they should be on most common
# modern distributions) or manually placing the file in the appropriate
# directory and creating symbolic links on System V or writing to rc.local on
# BSD-compatible systems. Systems requiring different treatment will be added
# here when we add support for them, but we will try to keep everything as
# generic as we can.
#
# In general, we try to behave as natively as we reasonably can on the most
# important target systems we support and to work well enough on as many others
# as possible, but in particular without trying to look perfectly native.
#
# To use this template as an init script, replace the following text sequences
# (wrapped in percent characters) with the values you need:
# COMMAND: Path to the service binary or script, with all required escaping for
# characters which are special in shell scripts.
# ARGUMENTS: The arguments to pass to the binary when starting the service,
# with all required escaping for characters which are special in shell scripts.
# SERVICE_NAME: The name of the service, using ASCII characters 33 to 126 only.
# DESCRIPTION: Short description of the service, suitable for use in texts like
# "DESCRIPTION successfully started", using Utf-8 characters 32 to 126 and 128
# and upwards.
## Time out in seconds when shutting down the service.
## If this is set to an empty value then the LSB init functions will not be
# used. This is intended for testing the fallback commands.
# Silently exit if the package was uninstalled but not purged.
test -r %COMMAND% || exit 0
## The function definition at the start of every non-trivial shell script!
abort()
{
log_failure_msg "$*"
exit 1
}
## Exit successfully.
{
log_success_msg "%DESCRIPTION% successfully started."
exit 0
}
## Set the error message.
{
}
shift
fi
# Process arguments.
action=""
error=""
prefix="/var"
while test x"${#}" != "x0"; do
case "${1}" in
test x"${#}" = "x1" &&
set_error "${1}: missing argument."
LSB_FUNCTIONS="${2}"
shift 2;;
--prefix)
test x"${#}" = "x1" &&
set_error "${1}: missing argument."
prefix="${2}"
shift 2;;
--help)
cat << EOF
Usage:
${0} {start|stop|restart|status} [<options>]
start|stop|restart|status
Start/stop/restart/report status for the service.
Options:
--lsb-functions <script>
Take the standard LSB init functions from <script> instead of from the
normal location, or use our own versions if <script> is an empty string.
--prefix <folder>
Use the folder <folder> for storing variable data instead of "/var". The
child folder "run" must exist.
EOF
exit 0;;
test -z "${action}" ||
set_error "More than one action requested."
action="${1}"
shift;;
*)
set_error "Unknown option \"${1}\". Try \"${0} --help\" for more information."
shift;;
esac
done
## Set Redhat and Fedora lock directory
LOCK_FOLDER="${prefix}/lock/subsys/"
LOCK_FILE="${LOCK_FOLDER}/%SERVICE_NAME%"
# Use LSB functions if available. Success and failure messages default to just
# "echo" if the LSB functions are not available, so call these functions with
# messages which clearly read as success or failure messages.
test -n "${LSB_FUNCTIONS}" && test -f "${LSB_FUNCTIONS}" &&
. "${LSB_FUNCTIONS}"
{
cat << EOF
${*}
EOF
}
{
cat << EOF
${*}
EOF
}
## Get the LSB standard PID-file name for a binary.
{
echo "${prefix}/run/${1##*/}.pid"
}
## Get the PID-file for a process like the LSB functions do ( "-p" or by name).
{
if test x"${1}" = "x-p"; then
echo "${2}"
else
pidfilename "${1}"
fi
}
## Read the pids from an LSB PID-file, checking that they are positive numbers.
{
pids=""
test -r "${1}" &&
done
echo "${pids}"
}
## Check whether the binary $1 with the pids $2... is running.
{
binary="${1}"
shift
return 0;;
esac
return 1
}
# We prefer our own implementations of pidofproc and killproc over falling back
# to distribution ones with unknown quirks.
{
test "x${1}" = "x-p" && shift 2
}
killproc()
{
test "x${1}" = "x-p" && shift 2
if test -n "${2}"; then
return 0
else
rm -f "${pidfile}"
kill "${pids}"
# Short busy wait for the process to terminate.
while test x"${stamp}" = x"`times`"; do
done
# Slow sleeping wait if it is still running.
for time in ${high}0 ${high}1 ${high}2 ${high}3 ${high}4 ${high}5 ${high}6 ${high}7 ${high}8 ${high}9; do
sleep 1
if test "${time}" = "${SHUT_DOWN_TIME_OUT}"; then
kill -9 "${pid}"
return 0
fi
done
done
return 0
fi
}
start()
{
pid="$!"
echo "${pid}" > "${pidfile}"
}
stop()
{
rm -f "${LOCK_FILE}"
log_success_msg "%DESCRIPTION% successfully stopped."
return 0
}
status()
{
test -n "${pid}" &&
{
echo "%SERVICE_NAME% running, process ${pid}"
exit 0
}
{
echo "%SERVICE_NAME% not running but PID-file present."
exit 1
}
test -f "${LOCK_FILE}" &&
{
echo "%SERVICE_NAME% not running but lock file present."
exit 2
}
echo "%SERVICE_NAME% not running."
exit 3
}
case "${action}" in
start;;
stop)
stop;;
stop;;
status || exit 0
stop
start;;
;;
status;;
esac