GNU bug report logs - #40672
shepherd fails to terminate processes after PID file timeout expiration

Previous Next

Package: guix;

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

Date: Thu, 16 Apr 2020 21:17:02 UTC

Severity: important

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

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 40672 in the body.
You can then email your comments to 40672 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#40672; Package guix. (Thu, 16 Apr 2020 21:17:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ludovic Courtès <ludo <at> gnu.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Thu, 16 Apr 2020 21:17:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: bug-guix <at> gnu.org
Subject: shepherd fails to terminate processes after PID file timeout
 expiration
Date: Thu, 16 Apr 2020 23:16:02 +0200
As discussed during <https://issues.guix.gnu.org/issue/40572>, in
Shepherd 0.7.0, if a process created with ‘fork+exec-command’ & co. with
#:pid-file fails to start before #:pid-file-timeout has expired,
shepherd marks it as failed but the process potentially just keeps
running.

Ludo’.




Severity set to 'important' from 'normal' Request was from Ludovic Courtès <ludo <at> gnu.org> to control <at> debbugs.gnu.org. (Fri, 17 Apr 2020 20:38:01 GMT) Full text and rfc822 format available.

Reply sent to Ludovic Courtès <ludo <at> gnu.org>:
You have taken responsibility. (Sat, 18 Apr 2020 15:15:02 GMT) Full text and rfc822 format available.

Notification sent to Ludovic Courtès <ludo <at> gnu.org>:
bug acknowledged by developer. (Sat, 18 Apr 2020 15:15:02 GMT) Full text and rfc822 format available.

Message #12 received at 40672-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: 40672-done <at> debbugs.gnu.org
Subject: Re: bug#40672: shepherd fails to terminate processes after PID file
 timeout expiration
Date: Sat, 18 Apr 2020 17:14:26 +0200
Ludovic Courtès <ludo <at> gnu.org> skribis:

> As discussed during <https://issues.guix.gnu.org/issue/40572>, in
> Shepherd 0.7.0, if a process created with ‘fork+exec-command’ & co. with
> #:pid-file fails to start before #:pid-file-timeout has expired,
> shepherd marks it as failed but the process potentially just keeps
> running.

Fixed in Shepherd commit 37dd896ce48908e4e3c56101fa07405070a6ce03.

Ludo'.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sun, 17 May 2020 11:24:06 GMT) Full text and rfc822 format available.

This bug report was last modified 3 years and 316 days ago.

Previous Next


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