Hi!
I would like to ask if runsvdir could by default be defined as a
subreaper on Linux. If it is already a PID 1, then there is no
difference, but sometimes it is not. In that case when an orphan
process happens under it, then it would be re-parented under the
runsvdir, mimicking the behavior when runsvdir runs as a PID 1.
runit is often used in Docker containers and sometimes you have a
wrapper script which spawns runsvdir as a child. In that case runsvdir
does not run as PID 1.
I have found a similar patch for Debian, but which requested this
feature on runsv. I think that might be misused for making process who
demonize in fact stay under runsv. Or maybe that is a future feature
of runit, not sure, but that can be discussion for some other thread.
I would like to ask that something similar to that patch is done for
runsvdir for now:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833048
This would really make it easier to use runit inside Docker.
A bit more about subreapers here:
https://unix.stackexchange.com/questions/250153/what-is-a-subreaper-process
Mitar
--
http://mitar.tnode.com/
https://twitter.com/mitar_m
Received on Mon Jan 30 2017 - 17:38:38 UTC