Re: s6-linux-init: SIGUSR1 and SIGUSR2

From: Colin Booth <cathexis_at_gmail.com>
Date: Mon, 22 Aug 2016 07:26:12 -0700

On Mon, Aug 22, 2016 at 6:35 AM, Laurent Bercot
<ska-supervision_at_skarnet.org> wrote:
> On 22/08/2016 14:02, Casper Ti. Vector wrote:
>>
>> Are SIGUSR1 and SIGUSR2 not just silently ignored in -S mode?
>
>
> Uuuuh, yes, my bad, they are.
> Sigh. I'm not sure what the right thing even is. Should they be ignored
> in -S mode? Should they do something? ISTR I kept them ignored *precisely*
> to avoid hardcoding policy into s6-svscan; it should probably remain that
> way.
My own $0.02 is that s6-svscan -S should ignore power state signals
(including SIGINT which it currently doesn't ignore). As for which
scheme s6-linux-init-maker supports when signals are redirected, I
think using busybox is an ok default since sysvinit is on the outs and
sysvinit's use of SIGUSR1 strikes me as an unfortunate misfeature.

Cheers!

-- 
"If the doors of perception were cleansed every thing would appear to
man as it is, infinite. For man has closed himself up, till he sees
all things thru' narrow chinks of his cavern."
  --  William Blake
Received on Mon Aug 22 2016 - 14:26:12 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:19 UTC