runit: why ignore SIGCONT for stages?

From: Leah Neukirchen <>
Date: Tue, 23 Nov 2021 13:17:58 +0100


During debugging a ksh issue (,
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:

      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.

Leah Neukirchen  <>
Received on Tue Nov 23 2021 - 13:17:58 CET

This archive was generated by hypermail 2.4.0 : Tue Nov 23 2021 - 13:18:30 CET