From: Steve Litt <slitt@troubleshooters.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: runit: why ignore SIGCONT for stages?
Date: Sat, 27 Nov 2021 15:45:44 -0500 [thread overview]
Message-ID: <20211127154544.750cef22@mydesk.domain.cxm> (raw)
In-Reply-To: <CADQ2Nw_XzzrCsdGDsP50E8rCYPZhYN_+p-MJ2yv1aBqafvJxnA@mail.gmail.com>
Guillermo said on Sat, 27 Nov 2021 17:05:14 -0300
>This was meant for the mailing list. I accidentally replied to the
>author instead. Sorry Leah!
>
>El mar, 23 nov 2021 a las 9:18, Leah Neukirchen escribió:
>>
>> [...] This seems to be due to runit(8) before execing
>> into the stages:
>>
>> sig_unblock(sig_cont);
>> sig_ignore(sig_cont);
>> ...
>> strerr_warn3(INFO, "enter stage: ", stage[st], 0);
>> execve(*prog, (char *const *)prog, envp);
>>
>> [...] Can someone explain why?
>
>I guess only the author can provide an authoritative answer, but this
>looks like a bug. It is possible that sig_uncatch() was meant here.
>That's what the code calls for the other two signals that runit(8)
>catches (SIGCHLD and SIGINT).
>
>sig_ignore() makes no sense here, wouldn't that make 'sv cont' useless
>for processes of the init system's supervision tree?
It would seem so, and yet sv cont mydaemon starts up a paused mydaemon.
So there's something we're missing.
SteveT
Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
prev parent reply other threads:[~2021-11-27 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 12:17 Leah Neukirchen
2021-11-23 18:28 ` Steve Litt
2021-11-27 20:05 ` Guillermo
2021-11-27 20:45 ` Steve Litt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211127154544.750cef22@mydesk.domain.cxm \
--to=slitt@troubleshooters.com \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).