From 8071261331863687f6f7b38b799808bb108e90ac Mon Sep 17 00:00:00 2001 From: Colin Booth Date: Thu, 22 Jan 2026 22:18:44 +0000 Subject: s6-frontend.html Minor language cleanup, nothing big. --- doc/s6-frontend.html | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) (limited to 'doc/s6-frontend.html') diff --git a/doc/s6-frontend.html b/doc/s6-frontend.html index df6b913..50ef7b0 100644 --- a/doc/s6-frontend.html +++ b/doc/s6-frontend.html @@ -55,19 +55,18 @@ performs the work described in the documents linked from the s

The separation between s6 and s6-frontend is really just a trick to avoid writing an additional parser for the s6-frontend.conf -configuration file. The execline -set of tools is a dependency of s6-frontend anyway, because s6-frontend uses -some if these tools to build complex command lines calling various parts of the -s6 ecosystem; so using the -envfile tool as well -to read the configuration was a natural fit. +configuration file. Using envfile to read the +configuration was a natural fit because the execline set of tools is used by +s6-frontend to build complex command lines.

That is why usage messages given by the various s6 foobar help commands print Usage: s6 foobar subcommand... but error messages, if they happen, print s6-frontend: fatal: error condition, because -the program where the error occurred is s6-frontend, not s6.

+the program where the error occurred is s6-frontend, not s6. +

Note that most error messages will print the name of another command, @@ -89,8 +88,8 @@ name of the program that prepends the error messages. various parts of the s6 ecosystem

  • Various programs from the s6 supervision suite or the s6-rc service manager, -invoked by s6-frontend, perform the work. When they succeed, it is transparent; -when they fail, they prepend the error message with their name.
  • +invoked by s6-frontend, perform the work. When they succeed it is transparent; +when they fail they prepend the error message with their name. -- cgit v1.3.1