will the setting achieved by this very ioctl() call survive after
exec()ing into another binary (s6-svscan/stage 2) ?
Testing on s6-linux-init 1.0.4.0 shows that a SIGWINCH is sent to
s6-svscan on kbrequest after s6-linux-init has performed the ioctl.
So, the answer seems to be yes.
Having
25.02.2020, 10:08, "Jonathan de Boyne Pollard"
:
> Yes. First: This is a kernel virtual terminal thing not a console
> thing. Strictly speaking, it is doing it wrongly to access it through
> the console device, which is not necessarily a KVT. Second: The
> mechanism does not require an open file d
25.02.2020, 10:08, "Jonathan de Boyne Pollard"
:
>> Of course, but once the fd is closed, /dev/console should not have
>> any impact on the process, so would a kbrequest still reach it?
>
> Yes. First: This is a kernel virtual terminal thing not a console
> thing. Strictly speaking, it is doing
24.02.2020, 23:25, "Laurent Bercot" :
> However, I was not aware that kbrequest needed a special ioctl call
> before it can be accepted, so thank you for that; I'll add the call
> to s6-l-i.
will the setting achieved by this very ioctl() call survive after
exec()ing into another binary (s6-svscan/
