On 30/04/2016 16:06, Guillermo wrote:
I think I made a mistake in that description. The s6rc-oneshot-runner
service is an s6-ipcserverd process that spawns s6-sudod processes.
And the program executed by s6-sudod gets its stdout and stderr from
the corresponding s6-sudoc process by default.
Some more background on this.
2016-04-02 14:42 GMT-03:00 Laurent Bercot:
>
> I have no idea what the TIOCSCTTY is for, though.
Apparently, on Linux and the BSDs, if 'fd' is an open file descriptor
to a terminal device, ioctl(fd, TIOCSCTTY, ...) (two or three
arguments) sets it as the
Consider a machine with an s6-linux-init-maker-style setup, that also
uses s6-rc in the stage2 and stage2_finish scripts. Longruns managed
by s6-rc without a 'producer-for' file in their definition directory
have their stdout and stderr redirected to the catch-all logger, and
so do oneshots via
