Subject: bug#40672: closed (Re: bug#40672: shepherd fails to terminate processes after PID file timeout expiration)

From: [email-masked] (GNU bug Tracking System)
Date: Sat, 18 Apr 2020 15:15:02 +0000

Your bug report

#40672: shepherd fails to terminate processes after PID file timeout expiration

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
40672: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40672
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#40672: shepherd fails to terminate processes after PID file timeout expiration
From: Ludovic Courtès <[email-masked]>
To: [email-masked]
Date: Sat, 18 Apr 2020 17:14:26 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Ludovic Courtès <[email-masked]> 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'.

Subject: shepherd fails to terminate processes after PID file timeout expiration
From: Ludovic Courtès <[email-masked]>
To: [email-masked]
Date: Thu, 16 Apr 2020 23:16:02 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

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’.