From 9059c09ef1e5e71d3b63754bbe1277338070955b Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sat, 20 Dec 2014 02:52:53 +0000 Subject: Doc fixes --- doc/s6-connlimit.html | 2 +- doc/s6-sudoc.html | 2 +- doc/s6-sudod.html | 2 +- doc/s6-tcpserver-access.html | 6 +++--- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/s6-connlimit.html b/doc/s6-connlimit.html index f0422e6..5008b4d 100644 --- a/doc/s6-connlimit.html +++ b/doc/s6-connlimit.html @@ -39,7 +39,7 @@ of ${PROTO}CONNMAX, s6-connlimit exits 1 with an error message.
  • Else it execs into prog....
  • If ${PROTO}CONNMAX is unset, s6-connlimit directly execs into prog... without performing any check: -no maximum number of connection has been defined.
    • +no maximum number of connections has been defined.

    Usage

    diff --git a/doc/s6-sudoc.html b/doc/s6-sudoc.html index 0ca9918..def09a9 100644 --- a/doc/s6-sudoc.html +++ b/doc/s6-sudoc.html @@ -65,7 +65,7 @@ default, timeoutrun is 0, meaning infinite. while the server program is still running, s6-sudod will send a SIGTERM and a SIGCONT to the server program - but this does not guarantee that it will die. If the server program keeps running, it might still read from the file that -was s6-sudoc's stdin, or write to the files that were s6-sudod's stdout or +was s6-sudoc's stdin, or write to the files that were s6-sudoc's stdout or stderr. This is a potential security risk. Administrators should audit their server programs to make sure this does not happen. diff --git a/doc/s6-sudod.html b/doc/s6-sudod.html index ac93219..d896d87 100644 --- a/doc/s6-sudod.html +++ b/doc/s6-sudod.html @@ -143,7 +143,7 @@ while the server program is still running, s6-sudod will send a SIGTERM and a SIGCONT to its child, then exit 1. However, sending a SIGTERM to the child does not guarantee that it will die; and if it keeps running, it might still read from the file that -was s6-sudoc's stdin, or write to the files that were s6-sudod's stdout or +was s6-sudoc's stdin, or write to the files that were s6-sudoc's stdout or stderr. This is a potential security risk. Administrators should audit their server programs to make sure this does not happen. diff --git a/doc/s6-tcpserver-access.html b/doc/s6-tcpserver-access.html index c7bb27a..cb758d9 100644 --- a/doc/s6-tcpserver-access.html +++ b/doc/s6-tcpserver-access.html @@ -170,7 +170,7 @@ client and converts it to canonical form. Then it checks it with the function. In other words, it tries to match broader and broader network prefixes of ip, from ip4/ip_32 to ip4/0.0.0.0_0 if ip is v4, or from -ip6/ip/128 to ip6/::_0 if ip +ip6/ip_128 to ip6/::_0 if ip is v6. If the result is:

    @@ -195,8 +195,8 @@ S6NET_ACCESSRULES_ALLOW.

    Note that even if the access check succeeds, the connection can still be -denied if paranoid mode has been required (-p) and a forward DNS query -on remotehost does not match ip. +denied if paranoid mode has been requested (-p) and a forward DNS +query on remotehost does not match ip.

    Environment and executable modifications

    -- cgit v1.2.3