File: yaws.init

package info (click to toggle)
yaws 2.2.0%2Bdfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 8,008 kB
  • sloc: erlang: 42,469; sh: 2,553; javascript: 1,459; makefile: 994; ansic: 890; lisp: 79; python: 34; xml: 12; php: 1
file content (141 lines) | stat: -rw-r--r-- 4,464 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
#! /bin/sh
### BEGIN INIT INFO
# Provides:          yaws
# Required-Start:    $network $remote_fs
# Should-Start:      $null
# Required-Stop:     $network $remote_fs
# Should-Stop:       $null
# Default-Start:     3 5
# Default-Stop:      0 1 2 6
# Short-Description: A high performance HTTP 1.1 webserver
# Description:       Yaws is a HTTP high perfomance 1.1 webserver
#                   particularly well suited for dynamic-content
#                   webapplications.
### END INIT INFO


YAWS_BIN=%bindir%/yaws

## By default we run with the default id
# YAWS_ID_OPTS=--id myserverid

conf="--conf %etcdir%/yaws/yaws.conf"

test -x $YAWS_BIN || exit 5



# Shell functions sourced from /etc/rc.status:
#      rc_check         check and set local and overall rc status
#      rc_status        check and set local and overall rc status
#      rc_status -v     ditto but be verbose in local rc status
#      rc_status -v -r  ditto and clear the local rc status
#      rc_failed        set local and overall rc status to failed
#      rc_failed <num>  set local and overall rc status to <num><num>
#      rc_reset         clear local rc status (overall remains)
#      rc_exit          exit appropriate to overall rc status
#      rc_active    checks whether a service is activated by symlinks
. /etc/rc.status

# First reset status of this service
rc_reset

# Return values acc. to LSB for all commands but status:
# 0 - success
# 1 - generic or unspecified error
# 2 - invalid or excess argument(s)
# 3 - unimplemented feature (e.g. "reload")
# 4 - insufficient privilege
# 5 - program is not installed
# 6 - program is not configured
# 7 - program is not running
#
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signalling is not supported) are
# considered a success.

case "$1" in
    start)
        echo -n "Starting YAWS"
        ## Start daemon with startproc(8). If this fails
        ## the echo return value is set appropriate.

        # NOTE: startproc returns 0, even if service is
        # already running to match LSB spec.
        startproc $YAWS_BIN --daemon --heart $YAWS_ID_OPTS $conf
        $YAWS_BIN $YAWS_ID_OPTS --wait-started=10 >/dev/null

        # Remember status and be verbose
        rc_status -v
        ;;
    stop)
        echo -n "Shutting down YAWS"
        ## Stop daemon with killproc(8) and if this fails
        ## set echo the echo return value.
        startproc $YAWS_BIN $YAWS_ID_OPTS --stop
        $YAWS_BIN $YAWS_ID_OPTS --wait-stopped=10 >/dev/null

        # Remember status and be verbose
        rc_status -v
        ;;
    try-restart)
        ## Stop the service and if this succeeds (i.e. the
        ## service was running before), start it again.
        ## Note: try-restart is not (yet) part of LSB (as of 0.7.5)
        $0 status >/dev/null && $0 restart

        # Remember status and be quiet
        rc_status
        ;;
    restart)
        ## Stop the service and regardless of whether it was
        ## running or not, start it again.
        $0 stop
        $0 start

         # Remember status and be quiet
        rc_status
        ;;
    force-reload)
        ## Signal the daemon to reload its config. Most daemons
        ## do this on signal 1 (SIGHUP).
        ## If it does not support it, restart.

        echo -n "Force Reload service YAWS"
        ## if it supports it:
        $YAWS_BIN  $YAWS_ID_OPTS --hup
        rc_status -v

        ;;
    reload)
        ## Like force-reload, but if daemon does not support
        ## signalling, do nothing (!)

        # If it supports signalling:

        startproc $YAWS_BIN $YAWS_ID_OPTS --hup
        rc_status -v

        ;;
    status)
        echo -n "Checking for service YAWS: "
        ## Check status with checkproc(8), if process is running
        ## checkproc will return with exit status 0.

        # Return value is slightly different for the status command:
        # 0 - service running
        # 1 - service dead, but /var/run/  pid  file exists
        # 2 - service dead, but /var/lock/ lock file exists
        # 3 - service not running

        # NOTE: checkproc returns LSB compliant status values.
        checkproc $YAWS_BIN $YAWS_ID_OPTS --status
        rc_status -v
        ;;
    *)
        echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload}"
        exit 1
        ;;
esac
rc_exit