|
From: | Ludovic Courtès |
Subject: | bug#56674: bug#58926: Shepherd becomes unresponsive after an interrupt |
Date: | Mon, 14 Nov 2022 17:32:35 +0100 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
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’.
[Prev in Thread] | Current Thread | [Next in Thread] |