On 14/03/2016 19:45, Brian Shore wrote:
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
Even better ! :)
--
Laurent
On Mon, Mar 14, 2016 at 11:18 AM, Laurent Bercot
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
On 14/03/2016 17:49, Jan Bramkamp wrote:
The correct solution would be to teach s6-svscan about SIGPWR and proxy it to
.s6-svscan/SIGPWR.
This.
SIGPWR is not a "traditional" signal to use to ask for a normal shutdown,
and it is a design mistake in lxc-stop to use it. SIGPWR has very specific
On 14/03/16 17:42, Jan Olszak wrote:
Hi!
We're running s6 in an lxc container.
lxc-stop sends SIGPWR to the init process (s6-svscan) to stop the
container, but SIGPWR isn't handled. It just gets discarded as if nothing
happened.
Is there a reason it works this way?
Thanks!
Jan
Probably beca
Hi!
We're running s6 in an lxc container.
lxc-stop sends SIGPWR to the init process (s6-svscan) to stop the
container, but SIGPWR isn't handled. It just gets discarded as if nothing
happened.
Is there a reason it works this way?
Thanks!
Jan
