Difference between revisions of "Initscripts/Writing rc.d scripts"
(gr; formality; bogus filenames) |
(update as discussed in Help_talk:Style/Article_summary_templates#Deprecation_of_summaries_and_overviews) |
||
(14 intermediate revisions by 9 users not shown) | |||
Line 1: | Line 1: | ||
− | [[Category:Boot process | + | [[Category:Boot process]] |
− | [[Category: | + | [[Category:Package development]] |
− | + | [[cs:Writing rc.d scripts]] | |
− | + | [[es:Writing rc.d scripts]] | |
− | {{ | + | [[zh-CN:Writing rc.d scripts]] |
− | {{ | + | {{Related articles start}} |
− | {{ | + | {{Related|Arch Boot Process}} |
− | {{ | + | {{Related|Daemon}} |
− | {{ | + | {{Related|rc.conf}} |
+ | {{Related articles end}} | ||
+ | {{Warning|Arch only supports [[systemd]]. Arch's old initscripts package is obsolete and is no longer supported. All Arch users need to move to systemd.}} | ||
− | + | [[Initscripts]] uses rc.d scripts to used to control the starting, stopping and restarting of [[Daemon|daemons]]. | |
− | ==Guideline== | + | == Guideline == |
− | *Source {{ | + | * Source {{ic|/etc/rc.conf}}, {{ic|/etc/rc.d/functions}}, and optionally {{ic|/etc/conf.d/DAEMON_NAME}}. |
− | *Arguments and other daemon options should be placed in {{ | + | * Arguments and other daemon options should be placed in {{ic|/etc/conf.d/DAEMON_NAME}}. This is done to separate configuration from logic and to keep a consistent style among daemon scripts. |
− | *Use functions in {{ | + | * Use functions in {{ic|/etc/rc.d/functions}} instead of duplicating their functionality. |
− | *Include at least start, stop and restart as arguments to the script. | + | * Include at least start, stop and restart as arguments to the script. |
− | ==Example== | + | == Available functions == |
− | The following is an example for ''crond''. Look in {{ | + | * There are some functions provided by {{ic|/etc/rc.d/functions}}: |
+ | ** {{Ic|stat_busy "''message''"}}: set status ''busy'' for printed message (e.g. <nowiki>Starting daemon [BUSY]</nowiki>) | ||
+ | ** {{Ic|stat_done}}: set status ''done'' (e.g. <nowiki>Starting daemon [DONE]</nowiki>) | ||
+ | ** {{Ic|stat_fail}}: set status ''failed'' (e.g. <nowiki>Starting daemon [FAILED]</nowiki>) | ||
+ | ** {{Ic|get_pid ''program''}}: get PID of the program | ||
+ | ** {{Ic|ck_pidfile ''PID-file'' ''program''}}: check whether PID-file is still valid for the program (e.g. <nowiki>ck_pidfile /var/run/daemon.pid daemon || rm -f /var/run/daemon.pid</nowiki>) | ||
+ | ** {{Ic|<nowiki>[add|rm]_daemon</nowiki> ''program''}}: add/remove program to running daemons (stored in {{ic|/run/daemons/}}) | ||
+ | |||
+ | Full list of functions is much longer and most possibilities (like way to control whether or not non-root users can launch daemon) are still undocumented and can be learned only from {{ic|/etc/rc.d/functions}} source. See also {{Ic|man rc.d}}. | ||
+ | |||
+ | == Example == | ||
+ | The following is an example for ''crond''. Look in {{ic|/etc/rc.d}} for greater variety. | ||
The configuration file: | The configuration file: | ||
− | {{ | + | {{hc|/etc/conf.d/crond|2=<nowiki>ARGS="-S -l info"</nowiki>}} |
The actual script: | The actual script: | ||
− | {{ | + | {{hc|/etc/rc.d/crond|2=<nowiki> |
#!/bin/bash | #!/bin/bash | ||
Line 35: | Line 48: | ||
[ -r /etc/conf.d/$DAEMON ] && . /etc/conf.d/$DAEMON | [ -r /etc/conf.d/$DAEMON ] && . /etc/conf.d/$DAEMON | ||
− | PID=$( | + | PID=$(get_pid $DAEMON) |
case "$1" in | case "$1" in |
Revision as of 13:35, 31 December 2013
Warning: Arch only supports systemd. Arch's old initscripts package is obsolete and is no longer supported. All Arch users need to move to systemd.
Initscripts uses rc.d scripts to used to control the starting, stopping and restarting of daemons.
Guideline
- Source
/etc/rc.conf
,/etc/rc.d/functions
, and optionally/etc/conf.d/DAEMON_NAME
. - Arguments and other daemon options should be placed in
/etc/conf.d/DAEMON_NAME
. This is done to separate configuration from logic and to keep a consistent style among daemon scripts. - Use functions in
/etc/rc.d/functions
instead of duplicating their functionality. - Include at least start, stop and restart as arguments to the script.
Available functions
- There are some functions provided by
/etc/rc.d/functions
:-
stat_busy "message"
: set status busy for printed message (e.g. Starting daemon [BUSY]) -
stat_done
: set status done (e.g. Starting daemon [DONE]) -
stat_fail
: set status failed (e.g. Starting daemon [FAILED]) -
get_pid program
: get PID of the program -
ck_pidfile PID-file program
: check whether PID-file is still valid for the program (e.g. ck_pidfile /var/run/daemon.pid daemon || rm -f /var/run/daemon.pid) -
[add|rm]_daemon program
: add/remove program to running daemons (stored in/run/daemons/
)
-
Full list of functions is much longer and most possibilities (like way to control whether or not non-root users can launch daemon) are still undocumented and can be learned only from /etc/rc.d/functions
source. See also man rc.d
.
Example
The following is an example for crond. Look in /etc/rc.d
for greater variety.
The configuration file:
/etc/conf.d/crond
ARGS="-S -l info"
The actual script:
/etc/rc.d/crond
#!/bin/bash . /etc/rc.conf . /etc/rc.d/functions DAEMON=crond ARGS= [ -r /etc/conf.d/$DAEMON ] && . /etc/conf.d/$DAEMON PID=$(get_pid $DAEMON) case "$1" in start) stat_busy "Starting $DAEMON" [ -z "$PID" ] && $DAEMON $ARGS &>/dev/null if [ $? = 0 ]; then add_daemon $DAEMON stat_done else stat_fail exit 1 fi ;; stop) stat_busy "Stopping $DAEMON" [ -n "$PID" ] && kill $PID &>/dev/null if [ $? = 0 ]; then rm_daemon $DAEMON stat_done else stat_fail exit 1 fi ;; restart) $0 stop sleep 1 $0 start ;; *) echo "usage: $0 {start|stop|restart}" esac