diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2020-09-16 12:04:55 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2020-09-16 12:04:55 +0000 |
| commit | b0fe68c13b04af8c098d53ea999bba6b7395163d (patch) | |
| tree | 298bab9f755edd10f4fd09c22beadb89f05f1be3 /doc/s6-svscan.html | |
| parent | 997b02adcc8384906339ea81ece5ba7244f3ef60 (diff) | |
| download | s6-b0fe68c13b04af8c098d53ea999bba6b7395163d.tar.xz | |
Documentation fixes, by flexibeast
Diffstat (limited to 'doc/s6-svscan.html')
| -rw-r--r-- | doc/s6-svscan.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/s6-svscan.html b/doc/s6-svscan.html index fc54cd9..3a93e00 100644 --- a/doc/s6-svscan.html +++ b/doc/s6-svscan.html @@ -32,7 +32,7 @@ the root or a branch of a <em>supervision tree</em>. <ul> <li> If given a <em>scandir</em> argument, s6-svscan switches to it. Else it uses -its current directory as <a href="scandir.html">scan directory</a>. </li> +its current directory as the <a href="scandir.html">scan directory</a>. </li> <li> It exits 100 if another s6-svscan process is already monitoring this <a href="scandir.html">scan directory</a>. </li> <li> If the <tt>./.s6-svscan</tt> control directory does not exist, @@ -174,7 +174,7 @@ command, s6-svscan runs a <em>reaper</em> routine. <p> The reaper acknowledges (via some -<a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/wait.html">wait()</a> +<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/wait.html">wait()</a> function), without blocking, every terminated child of s6-svscan, even ones it does not know it has. This is especially important when <a href="s6-svscan-1.html">s6-svscan is run as process 1</a>. @@ -204,7 +204,7 @@ It skips names starting with dots. It will not create services for more than <p> For every new subdirectory <em>dir</em> it finds, the scanner spawns a <a href="s6-supervise.html">s6-supervise</a> process on it. If -<em>dir</em><tt>/log</tt> exists, it spawns a s6-supervise process on +<em>dir</em><tt>/log</tt> exists, it spawns an s6-supervise process on both <em>dir</em> and <em>dir</em><tt>/log</tt>, and maintains a never-closing pipe from the service's stdout to the logger's stdin. This is <em>starting the service</em>, with or without a corresponding |