Hello,
El vie, 22 nov 2024 a las 20:24, Paul Sopka escribió:
>
> 1. When I redirect the file descriptors 1 and 2 like above, I get, as
> expected,
> no output on console/tty during the boot process,
> but I do get that when using s6-linux-init.
If I understand correctly, it is the combined effect of:
* s6-linux-init (the program) dup()'ing standard error, and passing
the resulting file descriptor to s6-svscan using its -X option.
* s6-svscan acting on the -X option and redirecting the standard error
of the catch-all logger's s6-supervise process to the console.
* If using the catch-all logger 'run' script generated by s6-linux-init-maker:
* The script redirecting standard error to standard output (with
execline's fdmove)
* The script invoking s6-log with the '1' action directive (copy
logged messages to standard output).
> 2. If I do not redirect them, I still get all the output on the catch
> all logger.
>
> 3. Using the script as above, my /run/uncaught-logs seems to get
> flooded with the same init messages over and over again during runtime.
I don't know. Do explicit redirections to
${TMPFSDIR}/service/s6-svscan-log/fifo only happen in the s6-init
script? No references to the FIFO elsewhere, like in
${BASEDIR}/scripts/rc.init?
G.
Received on Mon Nov 25 2024 - 02:28:22 CET