From ab87c7b64a7ea6a72149832cd86a12c3319d88e3 Mon Sep 17 00:00:00 2001 From: Gerrit Pape Date: Wed, 28 Jul 2004 15:58:22 +0000 Subject: * doc/runlevels.html, doc/upgrade.html, doc/useinit.html, man/runsvdir.8, man/runsvchdir.8: minor changes in wording, notations. --- doc/runsvdir.8.html | 54 ++++++++++++++++++++++++++--------------------------- 1 file changed, 27 insertions(+), 27 deletions(-) (limited to 'doc/runsvdir.8.html') diff --git a/doc/runsvdir.8.html b/doc/runsvdir.8.html index 606a44b..691ccac 100644 --- a/doc/runsvdir.8.html +++ b/doc/runsvdir.8.html @@ -17,37 +17,37 @@ runsvdir - starts and monitors a collection of runsv(8) processes dir must be a directory. log is a space holder for a readproctitle log, and must be at least seven characters long or absent.

-runsvdir starts a runsv(8) process for each subdirectory in dir, up to -a limit of 1000 subdirectories. runsvdir skips subdirectory names starting -with dots. runsv(8) must be in runsvdir’s PATH.

-At least every five seconds, -runsvdir checks if dir has changed. If it sees a new subdirectory in dir, -it starts a new runsv(8) process. If it sees an old sudirectory where a -runsv(8) process has exited, it restarts the runsv(8) process. If runsvdir -sees a subdirectory being removed that was previously there, it sends the -corresponding runsv(8) process a TERM signal, stops monitoring this process, -and so does not restart the runsv(8) process if it exits.

-If the log argument -is given to runsvdir, all output to standard error is redirected to this -log, which is similar to the readproctitle(8) log. To see the most recent -error messages, use a process-listing tool such as ps(1). runsvdir writes -a dot to the readproctitle log every 15 minutes so that old error messages -expire.

-Normally runsvdir is started by runit(8) in stage 2. +runsvdir starts a runsv(8) process for each subdirectory in the services +directory dir, up to a limit of 1000 subdirectories. runsvdir skips subdirectory +names starting with dots. runsv(8) must be in runsvdir’s PATH.

+At least every +five seconds, runsvdir checks if dir has changed. If it sees a new subdirectory +in services directory dir, it starts a new runsv(8) process. If it sees +an old sudirectory where a runsv(8) process has exited, it restarts the +runsv(8) process. If runsvdir sees a subdirectory being removed that was +previously there, it sends the corresponding runsv(8) process a TERM signal, +stops monitoring this process, and so does not restart the runsv(8) process +if it exits.

+If the log argument is given to runsvdir, all output to standard +error is redirected to this log, which is similar to the readproctitle(8) +log. To see the most recent error messages, use a process-listing tool such +as ps(1). runsvdir writes a dot to the readproctitle log every 15 minutes +so that old error messages expire.

+Normally runsvdir is started by runit(8) +in stage 2.

Signals

-If runsvdir -receives a TERM signal, it exits with 0 immediately.

-If runsvdir receives -a HUP signal, it sends a TERM signal to each runsv(8) process it is monitoring -and then exits with 111. +If runsvdir receives a TERM signal, it exits with 0 immediately. +

+If runsvdir receives a HUP signal, it sends a TERM signal to each runsv(8) +process it is monitoring and then exits with 111.

See Also

-runsv(8), runit(8), runit-init(8), runsvchdir(8), -runsvctrl(8), runsvstat(8), chpst(8), svlogd(8), utmpset(8), svwaitdown(8), -svwaitup(8)

+runsv(8), runit(8), +runit-init(8), runsvchdir(8), runsvctrl(8), runsvstat(8), chpst(8), svlogd(8), +utmpset(8), svwaitdown(8), svwaitup(8)

http://smarden.org/runit/

Author

-Gerrit Pape <pape@smarden.org> -

+Gerrit +Pape <pape@smarden.org>

Table of Contents

-- cgit 1.4.1