From: "Ludovic Courtès" <ludo@gnu.org>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 41507@debbugs.gnu.org
Subject: [bug#41507] [PATCH Shepherd 0/2] Use 'signalfd' on GNU/Linux
Date: Mon, 25 May 2020 09:37:18 +0200 [thread overview]
Message-ID: <87tv04wjm9.fsf@gnu.org> (raw)
In-Reply-To: <87o8qd2wos.fsf@jlicht.xyz> (Jelle Licht's message of "Sun, 24 May 2020 17:13:07 +0200")
Hi Jelle,
Jelle Licht <jlicht@fsfe.org> skribis:
> I am extremely happy to see that you got this to work; I bashed my head
> against a wall getting the signal-handling thread to block the right
> signals. This does seem like something that should be in guile proper
> rather than shepherd though.
Oh right, you had first-hand experience fiddling with this!
Yeah ideally Guile would provide some ‘signalfd’ support. I’m not sure
exactly how that should work. It’s easier to have ad-hoc support in the
Shepherd in the meantime.
> As I read it, you need to set up a signalfd handlers for specific
> signals before ever calling `sigaction'. Does this not have an impact on
> being able to do some forms of REPL-driven development with shepherd?
It depends, I don’t test things like SIGCHLD handling from the REPL
anyway. :-)
> Perhaps it makes sense to document this gotcha (and some of its
> implications) in a location other than an inline comment in
> `maybe-signal-port'.
Where would you document that? Currently, one gets a warning if signals
cannot be properly blocked.
Thanks for your feedback!
Ludo’.
next prev parent reply other threads:[~2020-05-25 7:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 14:27 [bug#41507] [PATCH Shepherd 0/2] Use 'signalfd' on GNU/Linux Ludovic Courtès
2020-05-24 14:36 ` [bug#41507] [PATCH Shepherd 1/2] system: Add support for 'signalfd' Ludovic Courtès
2020-05-24 14:37 ` [bug#41507] [PATCH Shepherd 2/2] shepherd: Use 'signalfd' when possible Ludovic Courtès
2020-05-25 12:31 ` Mathieu Othacehe
2020-05-26 22:13 ` bug#41507: " Ludovic Courtès
2020-05-27 5:45 ` [bug#41507] " Jan Nieuwenhuizen
2020-05-27 9:23 ` Ludovic Courtès
2020-05-30 17:44 ` Ludovic Courtès
2020-06-02 7:00 ` Mathieu Othacehe
2020-06-02 21:38 ` Ludovic Courtès
2020-05-24 15:13 ` [bug#41507] [PATCH Shepherd 0/2] Use 'signalfd' on GNU/Linux Jelle Licht
2020-05-25 7:37 ` Ludovic Courtès [this message]
2020-05-25 8:02 ` Jelle Licht
2020-05-26 21:32 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv04wjm9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41507@debbugs.gnu.org \
--cc=jlicht@fsfe.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).