(I'm so lagging behind...) 2015-10-15 7:47 GMT-03:00 Laurent Bercot: > > Additionally, the new s6 version features a new "-s" switch to > s6-svscan, that makes it possible to configure s6-svscan's behaviour > when it receives certain signals. This is useful, for instance, for > Ctrl-Alt-Del management when s6-svscan is used as process 1.
Interesting. BusyBox poweroff can now work with s6-svscan if there's an appropriate .s6-svscan/SIGUSR2 script, I tested it. I suppose runit-init, if called as 'init 0', would work too with an appropriate .s6-svscan/SIGCONT script, although that I cannot test. So, I don't know if the handler scripts for diverted signals that the new version of s6-linux-init-maker generates are intended to be compatible with BusyBox. But if that's the intention, then the ones for SIGUSR1 and SIGUSR2 are inverted: I think that the signal sent by 'busybox halt' to process 1 is SIGUSR1, so its handler should be the one calling s6-svscanctl -0 $tmpfsdir/service, and the signal sent by 'busybox poweroff' is SIGUSR2, so its handler should be the one calling s6-svscanctl -7 $tmpfsdir/service. And speaking of s6-linux-init-maker, the -e VAR=VALUE option generates a $basedir/env/VAR file that doesn't have a trailing newline after VALUE, although I don't know if s6-envdir cares. Thanks, G.