On Fri, Jan 06, 2017 at 11:38:24AM +0300, Dmitry Bogatov wrote: > > Package: runit > > Version: 1.7.2-1 > > Severity: wishlist > > > > Hi, > > > > it would be great to be able to use runit to supervise processes running in > > vserver guests. > > > > Using a kludge, this is already sort of possible; see > > http://linux-vserver.org/Running_runit-supervised_services_inside_a_vserver > > > > Essentially, the only addition needed is to do something like > > > > xid_t xid = vc_get_task_xid(child); > > vc_ctx_kill(xid, child, signal); > > > > instead of just kill(), provided vserver support is enabled in runit and the > > kernel. > > control: tags -1 +moreinfo > > Is there still someone who wish to make this change? If there, I still > oppose of introducing dependency. Even optional. Especially optional.
I've become used to living without this functionality but I still think it would be useful, also for containers different from linux-vserver. I suppose introducing a new dependency could be avoided thusly: in runsvdir, instead of invoking runsv for each directory, check whether the directory contains a file called runsv, and if it does, launch that instead of runsv. This would be totally backwards compatible. This change would allow people to use runsv replacements that expose the same interface to runsvdir(8) and sv(8) but for example support managing children that run in a different pid namespace. Andras -- Good literature is about Love and War. Trash fiction is about Sex and Violence.
