From: "Ludovic Courtès" <ludo@gnu.org>
To: 56674@debbugs.gnu.org
Cc: Mathieu Othacehe <othacehe@gnu.org>, 58926@debbugs.gnu.org
Subject: bug#58926: Shepherd becomes unresponsive after an interrupt
Date: Mon, 14 Nov 2022 17:32:35 +0100 [thread overview]
Message-ID: <87wn7xo5ss.fsf_-_@gnu.org> (raw)
In-Reply-To: <87o7tabg2x.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 14 Nov 2022 00:16:38 +0100")
Hello!
Ludovic Courtès <ludo@gnu.org> skribis:
> These fresh Shepherd commits install a non-blocking ‘system*’ replacement:
>
> 975b0aa service: Provide a non-blocking replacement of 'system*'.
> 039c7a8 service: Spawn a fiber responsible for process monitoring.
>
> We’ll have to do more testing and probably go for a 0.9.3 release soon.
Shepherd commit ada88074f0ab7551fd0f3dce8bf06de971382e79 passes my
tests. It definitely solves the wireguard example and similar things
(uses of ‘system*’ in service constructors/destructors); I can’t tell
for sure about nginx because I haven’t been able to reproduce it in a
VM. I’m interested in ways to reproduce it.
It does look like we could go with 0.9.3 real soon now.
Ludo’.
next prev parent reply other threads:[~2022-11-14 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 21:39 bug#56674: [Shepherd] Use of ‘waitpid’, ‘system*’, etc. in service code can cause deadlocks Ludovic Courtès
2022-07-20 23:48 ` Maxime Devos
2022-07-21 15:39 ` Ludovic Courtès
2022-08-13 14:59 ` Maxime Devos
2022-11-13 23:16 ` Ludovic Courtès
2022-11-14 16:32 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-31 12:44 bug#58926: Shepherd becomes unresponsive after an interrupt Mathieu Othacehe
2022-11-10 9:59 ` Ludovic Courtès
2022-11-12 18:10 ` Ludovic Courtès
2022-11-12 18:28 ` 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=87wn7xo5ss.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=56674@debbugs.gnu.org \
--cc=58926@debbugs.gnu.org \
--cc=othacehe@gnu.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).