>but when using such a catch-all logger to log s6-svscan's own output
>there is no need for the "rc" service to have its own logger since
>everything it outputs goes into this catch-all logger.
That's the end goal. That's what s6-linux-init-1.0.0.0 does.
What you call the "rc" service is named "runleveld" in s6-linux-init,
and it is just a service spawning a "s6-rc -pu change" process with
the argument you give to the telinit command. Its output naturally
goes to the catch-all logger.
Manual invocations of s6-rc are of course possible, in which case
the output will go to the user's terminal. runleveld is only
involved at boot time (well, not really, but the "runlevel" script,
that invokes the service manager, is spawned with the same
environment) and shutdown time, and on telinit invocation.
--
Laurent
Received on Sun May 19 2019 - 23:12:47 UTC