From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: runit: add support for SIGPWR signal
Date: Thu, 19 Mar 2020 14:50:56 +0100 [thread overview]
Message-ID: <20200319135056.W3sdnijvgECxrA8q-mXT0LBuSfvDIaXj9Ol7E6a9MuU@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: 894 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/20098#issuecomment-601189877
Comment:
I'm not completely happy with it, I would like to have a mechanism to completely disable sigpwr for non containers and users who may run a UPS that sends sigpwr but don't want this to shutdown the system or handle in some other way.
This also requires man page updates, we shouldn't just change how init behaves when it is signaled without documenting it, and considering edge cases.
I would add `/etc/runit/sigpwr` which is checked for for existence and executable bit.
Create it from our core services, and `chmod u+x` it if it is a "container" system.
This would not change anything for normal users, introduce the wanted behavior for "containers" and allows users with USPs that send a signal to pid 1 to enable it by `chmod u+x` the file.
next prev parent reply other threads:[~2020-03-19 13:50 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
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 [this message]
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=20200319135056.W3sdnijvgECxrA8q-mXT0LBuSfvDIaXj9Ol7E6a9MuU@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).