From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: runit: add support for SIGPWR signal
Date: Sun, 15 Mar 2020 19:00:40 +0100 [thread overview]
Message-ID: <20200315180040.J3FOKWmhJXrYp2U-ev4lHj7BAuuRUKgpIqNyJnrRrtM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20098@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/20098#issuecomment-599243492
Comment:
> SIGPWR is sent to init (process 1) directly, so no need to create any files (like stopit). Runit also reboots on getting SIGCONT (it is also not configurable)
Its configurable through the `/etc/runit/stopit` file. If the file doesn't exist or is not `S_IXUSR`, then runit won't shutdown.
This makes sure only `runit-init 0` can bring down runit, not a random SIGCONT or SIGINT.
Edit: this is as far as I know the whole deal about `stopit`, otherwise only `reboot` would exist.
next prev parent reply other threads:[~2020-03-15 18:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20098@inbox.vuxu.org>
2020-03-15 13:07 ` xtraeme
2020-03-15 14:30 ` Duncaen
2020-03-15 14:39 ` leahneukirchen
2020-03-15 15:24 ` innerspacepilot
2020-03-15 17:59 ` Duncaen
2020-03-15 18:00 ` Duncaen
2020-03-15 18:00 ` Duncaen
2020-03-15 18:00 ` Duncaen [this message]
2020-03-15 18:00 ` Duncaen
2020-03-15 18:07 ` Duncaen
2020-03-15 18:12 ` Duncaen
2020-03-16 8:00 ` innerspacepilot
2020-03-16 8:17 ` innerspacepilot
2020-03-16 9:40 ` innerspacepilot
2020-03-18 12:26 ` xtraeme
2020-03-19 13:23 ` Gottox
2020-03-19 13:50 ` Duncaen
2020-03-19 13:51 ` Duncaen
2020-03-19 13:54 ` xtraeme
2020-03-20 6:50 ` innerspacepilot
2020-03-20 6:50 ` [PR PATCH] [Closed]: " innerspacepilot
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=20200315180040.J3FOKWmhJXrYp2U-ev4lHj7BAuuRUKgpIqNyJnrRrtM@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).