supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Leah Neukirchen <leah@vuxu.org>
To: supervision@list.skarnet.org
Subject: runit: why ignore SIGCONT for stages?
Date: Tue, 23 Nov 2021 13:17:58 +0100	[thread overview]
Message-ID: <87tug3vzex.fsf@vuxu.org> (raw)

Hello,

During debugging a ksh issue (https://github.com/ksh93/ksh/issues/301),
we noticed that many processes on a Void Linux system booted with runit
are ignoring SIGCONT.  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);

This code has been there since 2001.  Can someone explain why?
Ignoring SIGCONT seems to be a no-op, and the default handler seems to
create no problems for other init systems.

Thanks,
-- 
Leah Neukirchen  <leah@vuxu.org>  https://leahneukirchen.org/

             reply	other threads:[~2021-11-23 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 12:17 Leah Neukirchen [this message]
2021-11-23 18:28 ` Steve Litt
2021-11-27 20:05 ` Guillermo
2021-11-27 20:45   ` Steve Litt

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=87tug3vzex.fsf@vuxu.org \
    --to=leah@vuxu.org \
    --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).