From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 2628 invoked from network); 23 Nov 2021 12:18:05 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 23 Nov 2021 12:18:05 -0000 Received: (qmail 11934 invoked by uid 89); 23 Nov 2021 12:18:26 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 11927 invoked from network); 23 Nov 2021 12:18:26 -0000 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:user-agent:date:message-id :mime-version; bh=EBceGhNAD0cMsdF2X664mZtKZiSmK4FW3YpIB5iQWNw=; b=rTvcqIx/p4GSeZp3FqxJ4ZMZWfBjyNOid5aKeqYd+cfTUOdhJhUGZay7psxm0l6Hfq gsF2zVzC4jjf/E/odCTNgsq91QQ3+QmTJxGeOiM3slKJNIP21JtDIEEL6KE9XPaxyORG D3hfl9oL8YgXAgMpao7Br4Qamy2PwSw4pZ69bIs1AHN4oMCZA8GLJacu539VMULgzbzT 0I8qNrktUWFXWGGE/O7q0f6sfCroHgDc///weAP3I2OtCuNizGzoy5dxfg5myy12VCuD YrLK/ZFgXIQwLoo9rfmtaTl9119IgBLwZOzFVtxK9MVCLsZ/Y83ZLDTnZyi8lTLvrqOC Vgyw== X-Gm-Message-State: AOAM531szH7tYdbkTUjUUUwssjdlkJbkwKNTYA1mLAVf7TDPIMO2OiRB nx/EgVWTltOLQ9JNpff4VzipSNyuG7Qyzg== X-Google-Smtp-Source: ABdhPJzNgeI9yuuUkjT38pRdKuF3wMvsRux4VnkPyo66HGTzFz2noUfag7rRvzrckivYqI0WJKApHg== X-Received: by 2002:a7b:c008:: with SMTP id c8mr2564756wmb.55.1637669879095; Tue, 23 Nov 2021 04:17:59 -0800 (PST) From: Leah Neukirchen To: supervision@list.skarnet.org Subject: runit: why ignore SIGCONT for stages? User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Date: Tue, 23 Nov 2021 13:17:58 +0100 Message-ID: <87tug3vzex.fsf@vuxu.org> MIME-Version: 1.0 Content-Type: text/plain 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 https://leahneukirchen.org/