From 8fe924c3da6ab919f512029a15464e77cbeede8a Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sun, 19 Nov 2023 03:05:39 +0000 Subject: Small bugfixes, update deps, update doc Signed-off-by: Laurent Bercot --- doc/index.html | 10 +++++----- doc/s6-tcpserver.html | 5 +++++ doc/s6-tcpserverd.html | 8 ++++++++ doc/upgrade.html | 8 ++++++++ 4 files changed, 26 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/index.html b/doc/index.html index 95294f2..b7209a9 100644 --- a/doc/index.html +++ b/doc/index.html @@ -55,27 +55,27 @@ as extensions to the s6 ecosystem.
  • A POSIX-compliant system with a standard C development environment
  • GNU make, version 3.81 or later
  • skalibs version -2.14.0.0 or later. It's a build-time requirement. It's also a run-time +2.14.0.1 or later. It's a build-time requirement. It's also a run-time requirement if you link against the shared version of the skalibs library.
  • (Optional, but recommended) execline version 2.9.4.0 or later. It's a build-time and run-time requirement.
  • s6 version -2.12.0.0 or later. It's a build-time and run-time requirement.
    • +2.12.0.1 or later. It's a build-time and run-time requirement.
  • s6-dns version -2.3.6.0 or later. It's a build-time requirement. It's also a run-time +2.3.7.0 or later. It's a build-time requirement. It's also a run-time requirement if you link against the shared version of the s6-dns libraries.
  • If you want to build the secure communication tools:
    • Either BearSSL version 0.6 or later.
      • -
    • Or LibreSSL version 3.7.3 +
    • Or LibreSSL version 3.8.2 or later.
    • Or OpenSSL version 1.1.1w or later and LibreTLS -version 3.7.0 or later.
      • +version 3.8.1 or later.
    The chosen library is a build-time requirement, and also a run-time requirement if you link against its shared version.
    • diff --git a/doc/s6-tcpserver.html b/doc/s6-tcpserver.html index 561c00f..f80fd18 100644 --- a/doc/s6-tcpserver.html +++ b/doc/s6-tcpserver.html @@ -135,6 +135,11 @@ that the name of the process is s6-tcpserverd, that's why. all the addresses of a machine no matter whether v4 or v6, then you need to run two s6-tcpserver processes: one on 0.0.0.0 and and one on ::. +
  • The option to make s6-tcpserver verbose is -v, without an +argument. This is different from the s6-tcpserverd +interface, where that would be -v 2. The difference exists because +s6-tcpserver follows the UCSPI tool +interface, whereas s6-tcpserverd has no such constraint.
    • diff --git a/doc/s6-tcpserverd.html b/doc/s6-tcpserverd.html index 6600a7b..55651e3 100644 --- a/doc/s6-tcpserverd.html +++ b/doc/s6-tcpserverd.html @@ -107,6 +107,14 @@ the listening socket. That program is normally which creates the socket itself; but it can be a different one if the socket is to be retrieved by another means, for instance by fd-passing from a fd-holding daemon (some people call this "socket activation"). +
  • The option to make s6-tcpserverd verbose is -v 2, where the +verbosity level is given as an argument, 0 being quiet, 1 normal and 2 verbose. +This is different from the s6-tcpserver +interface, where -v without an argument would indicate extra verbosity. +The difference exists because +s6-tcpserver follows the UCSPI tool +interface, whereas s6-tcpserverd has no such constraint, and giving the +verbosity level as a number is a better interface.
    • diff --git a/doc/upgrade.html b/doc/upgrade.html index a688976..4ff12d3 100644 --- a/doc/upgrade.html +++ b/doc/upgrade.html @@ -21,6 +21,14 @@

    in 2.7.0.0