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
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
#!/bin/bash
# Copyright 1999-2004 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
source /sbin/functions.sh
if [ "${RC_NOCOLOR}" = "yes" ]
then
unset BLUE GREEN OFF CYAN
else
BLUE="\033[34;01m"
GREEN="\033[32;01m"
OFF="\033[0m"
CYAN="\033[36;01m"
fi
myscript="${1}"
if [ -L "${1}" ]
then
myservice="$(readlink "${1}")"
else
myservice=${1}
fi
myservice=${myservice##*/}
echo -e "
${GREEN}Gentoo Linux RC-Scripts; ${BLUE}http://www.gentoo.org/${OFF}
Copyright 1999-2004 Gentoo Foundation; Distributed under the GPL
Usage: ${CYAN}${myservice}${OFF} < ${GREEN}flags${OFF} > [ ${GREEN}options${OFF} ]
${CYAN}Options:${OFF}
${GREEN}start${OFF}
Start service, as well as the services it depends on (if not already
started).
${GREEN}stop${OFF}
Stop service, as well as the services that depend on it (if not already
stopped).
${GREEN}restart${OFF}
Restart service, as well as the services that depend on it.
Note to developers: If this function is replaced with a custom one,
'svc_start' and 'svc_stop' should be used instead of 'start' and
'stop' to restart the service. This is so that the dependencies
can be handled correctly. Refer to the portmap rc-script for an
example.
${GREEN}pause${OFF}
Same as 'stop', but the services that depends on it, will not be
stopped.
${GREEN}zap${OFF}
Reset a service that is currently stopped, but still marked as started,
to the stopped state. Basically for killing zombie services.
${GREEN}status${OFF}
Prints \"status: started\" if the service is running, else it
prints \"status: stopped\".
Note that if the '--quiet' flag is given, it will return true if the
service is running, else false.
${GREEN}ineed|iuse${OFF}
List the services this one depends on. Consult the section about
dependencies for more info on the different types of dependencies.
${GREEN}needsme|usesme${OFF}
List the services that depend on this one. Consult the section about
dependencies for more info on the different types of dependencies.
${GREEN}broken${OFF}
List the missing or broken dependencies of type 'need' this service
depends on.
${CYAN}Flags:${OFF}
${GREEN}--quiet${OFF}
Suppress output to stdout, except if:
1) It is a warning, then output to stdout
2) It is an error, then output to stderr
${GREEN}--nocolor${OFF}
Suppress the use of colors.
${CYAN}Dependencies:${OFF}
This is the heart of the Gentoo RC-Scripts, as it determines the order
in which services gets started, and also to some extend what services
get started in the first place.
The following example demonstrates how to use dependencies in
rc-scripts:
depend() {
need foo bar
use ray
}
Here we have foo and bar as dependencies of type 'need', and ray of
type 'use'. You can have as many dependencies of each type as needed, as
long as there is only one entry for each type, listing all its dependencies
on one line only.
${GREEN}need${OFF}
These are all the services needed for this service to start. If any service
in the 'need' line is not started, it will be started even if it is not
in the current, or 'boot' runlevel, and then this service will be started.
If any services in the 'need' line fails to start or is missing, this
service will never be started.
${GREEN}use${OFF}
This can be seen as representing optional services this service depends on
that are not critical for it to start. For any service in the 'use' line,
it must be added to the 'boot' or current runlevel to be considered a valid
'use' dependency. It can also be used to determine startup order.
${GREEN}before${OFF}
This, together with the 'after' dependency type, can be used to control
startup order. In core, 'before' and 'after' do not denote a dependency,
but should be used for order changes that will only be honoured during
a change of runlevel. All services listed will get started *after* the
current service. In other words, this service will get started *before*
all listed services.
${GREEN}after${OFF}
All services listed will be started *before* the current service. Have a
look at 'before' for more info.
${GREEN}provide${OFF}
This is not really a dependency type, rather it will enable you to create
virtual services. This is useful if there is more than one version of
a specific service type, system loggers or crons for instance. Just
have each system logger provide 'logger', and make all services in need
of a system logger depend on 'logger'. This should make things much more
generic.
Note that the 'need', 'use', 'before' and 'after' dependeny types can have '*'
as argument. Having:
depend() {
before *
}
will make the service start first in the current runlevel, and:
depend() {
after *
}
will make the service the last to start.
You should however be careful how you use this, as I really will not
recommend using it with the 'need' or 'use' dependency type ... you have
been warned!
${CYAN}Configuration files:${OFF}
There are two files which will be sourced for possible configuration by
the rc-scripts. They are (sourced from top to bottom):
/etc/conf.d/${myservice}
/etc/rc.conf
${CYAN}Management:${OFF}
Services are added and removed via the 'rc-update' tool. Running it without
arguments should give sufficient help.
"
|
GitWeb