On Mon, Mar 14, 2016 at 11:18 AM, Laurent Bercot
<ska-supervision_at_skarnet.org> wrote:
> The correct workaround is indeed to use the -s option to s6-svscan and
> write appropriate .s6-svscan/SIG* scripts to handle various signals in a
> personalized way.
Alternatively, change LXC's behavior via the configuraiton file. We
use the following with runit (which expects SIGCONT for shutdown):
lxc.haltsignal = SIGCONT
lxc.stopsignal = SIGCONT
--
Brian Shore
Senior Systems Engineer, Security Architect
Network Redux, LLC
5200 SW Macadam Ave Ste 450
Portland, Oregon 97239
Desk: 503-274-9905 x503
Received on Mon Mar 14 2016 - 18:45:56 UTC