From 20c7d8e1b328155145ce9e8648435e127b60c208 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Wed, 14 Jan 2015 01:21:41 +0000 Subject: Doc update --- doc/s6-tcpserver6.html | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'doc/s6-tcpserver6.html') diff --git a/doc/s6-tcpserver6.html b/doc/s6-tcpserver6.html index e571010..42f0c92 100644 --- a/doc/s6-tcpserver6.html +++ b/doc/s6-tcpserver6.html @@ -40,6 +40,9 @@ and stdout writing to it.
  • Depending on the verbosity level, it logs what it does to stderr.
  • It runs until killed by a signal. Depending on the received signal, it may kill its children before exiting.
    • +
  • s6-tcpserver6 actually doesn't do any of this itself. It is +a wrapper, rewriting the command line and executing into a chain +of programs that perform those duties.

    • Environment variables

    @@ -116,6 +119,16 @@ used to serve IPv4 addresses.
  • s6-tcpserver6 will only work if the underlying skalibs has been compiled with IPv6 support.
    • +
  • In previous releases of s6-networking, s6-tcpserver6 was +monolithic: it did the work of +s6-tcpserver6-socketbinder, +s6-applyuidgid and +s6-tcpserver6d itself. The functionality has now +been split into several different programs because some service startup +schemes require the daemon to get its socket from an external +program instead of creating and binding it itself. The most obvious +application of this is upgrading a long-lived process without +losing existing connections.
    • -- cgit v1.2.3