GNU bug report logs - #41507
[PATCH Shepherd 0/2] Use 'signalfd' on GNU/Linux

Previous Next

Package: guix-patches;

Reported by: Ludovic Courtès <ludo <at> gnu.org>

Date: Sun, 24 May 2020 14:28:01 UTC

Severity: normal

Tags: patch

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Jelle Licht <jlicht <at> fsfe.org>
To: Ludovic Courtès <ludo <at> gnu.org>, 41507 <at> debbugs.gnu.org
Subject: [bug#41507] [PATCH Shepherd 0/2] Use 'signalfd' on GNU/Linux
Date: Sun, 24 May 2020 17:13:07 +0200
Ludovic Courtès <ludo <at> gnu.org> writes:

> Hello!
>
> This patch series allows shepherd to use ‘signalfd’ on GNU/Linux.

[...] 

> Thoughts?

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.

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?
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'.

Thanks for getting this to work nonetheless!
 - Jelle





This bug report was last modified 4 years and 350 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.