From e4821d7a10ee2096b689a66baa9b974d51339bc3 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Tue, 23 May 2017 11:05:54 +0000 Subject: Switch doc to schemeless URLs --- doc/s6-rc-compile.html | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) (limited to 'doc/s6-rc-compile.html') diff --git a/doc/s6-rc-compile.html b/doc/s6-rc-compile.html index 453c6ac..d78e7ad 100644 --- a/doc/s6-rc-compile.html +++ b/doc/s6-rc-compile.html @@ -6,14 +6,14 @@ s6-rc: the s6-rc-compile program - +

s6-rc
-Software
-skarnet.org +Software
+skarnet.org

The s6-rc-compile program

@@ -73,7 +73,7 @@ use this database with s6-rc to start and stop services. gids must be a comma-separated list of numerical GIDs.

-h fdhuser : arrange for the -s6-fdholder-daemon +s6-fdholder-daemon program, which maintains the pipes for the longrun pipelines, to run as user fdhuser. By default, it runs as the user owning the supervision tree, i.e. most likely root.

@@ -201,7 +201,7 @@ complain and exit 1.

Two regular files named up and down, which must each contain a single Unix command line. The files will be interpreted by the -execlineb +execlineb lexer at compile time and the results will be stored into the compiled database in an internal form. up will be run when the service is started, and down will be executed when the service @@ -215,10 +215,10 @@ does nothing and always succeeds.

up and down are interpreted by -execlineb, but +execlineb, but that does not mean they have to be entirely written in the -execline language. The -execlineb +execline language. The +execlineb lexer is only used because it can compile a Unix command line from a text file and store the compiled result, whereas a shell would have to be invoked everytime the script is run. There are many ways to write up and @@ -248,7 +248,7 @@ You don't.

The s6-rc service definition directory for a longrun service is similar to -a s6 service +a s6 service directory, but there are a few differences:

finish

notification-fd

timeout-kill

timeout-finish

nosetsid

service directory

s6-supervise

Optional directories named data and env. These will be copied verbatim into the generated service directory.

Note that you cannot create a ./down file for -s6-supervise +s6-supervise in a generated service directory. Even if such a file exists in the definition directory, it will be ignored - it will not be replicated in the service directory. @@ -369,7 +369,7 @@ detect and reject cycles as well as collisions.

The pipe linking a producer with a consumer is created and stored at run-time in a -s6-fdholder-daemon +s6-fdholder-daemon instance managed by an automatically generated longrun service named s6rc-fdholder.

busybox

skarnet.org

/etc