From b0fe68c13b04af8c098d53ea999bba6b7395163d Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Wed, 16 Sep 2020 12:04:55 +0000 Subject: Documentation fixes, by flexibeast --- doc/servicedir.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/servicedir.html') diff --git a/doc/servicedir.html b/doc/servicedir.html index 044406e..a7b9dd1 100644 --- a/doc/servicedir.html +++ b/doc/servicedir.html @@ -71,7 +71,7 @@ to log stderr as well, so the run script should make sure that its stderr goes into the log pipe. This is achieved by fdmove -c 2 1 in execline, -and exec 2>&1 in shell. +and exec 2>&1 in shell.
  • adjust the environment for your foo daemon. Normally the run script inherits its environment from s6-supervise, @@ -209,7 +209,7 @@ directory.

    -

    Where to store my service directories ?

    +

    Where should I store my service directories?

    @@ -241,7 +241,7 @@ collection. This is the easy setup, not requiring an external init system to mount your filesystems - however, it requires your root filesystem to be read-write, which is unacceptable if you are concerned with reliability - if you are, for instance, designing an embedded platform.

    • -
  • Some people like to have +
  • Some people like to have their service directories in a read-only filesystem, with supervise symlinks pointing to various places in writable filesystems. This setup looks a bit complex to me: it requires careful handling of the writable -- cgit v1.2.3