On Tue, Jan 02, 2018 at 08:33:18AM -0800, Earl Chew via skaware wrote:
> I do not think that my suggestion of placing the children of s6-svscan in a
> separate process group from s6-svscan itself changes any of these
> objectives. Each service would continue to apply its own session leader role
> by default, and explicit requests to tear down the supervision tree and the
> supervised processes should do just that.

Perhaps this would achieve what you want:
# mv /path/to/s6-supervise /path/to/s6-supervise.bin
# > /path/to/s6-supervise printf \
'#!/bin/sh\nexec /path/to/setsid /path/to/s6-supervise.bin $@\n'
(Similar tricks have been used to endow /path/to/s6-supervise with other
"capabilities" without really modify the source code; also note that the
shell would introduce additional variables into the environment, so you
can also consider using execline.)
--
My current OpenPGP key:
RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19)
7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C