GNU bug report logs - #63982
[Shepherd] shepherd does not handle signals after 'daemonize'

Previous Next

Package: guix;

Reported by: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Date: Fri, 9 Jun 2023 17:14:01 UTC

Severity: normal

Tags: moreinfo

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: nils <at> landt.email
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: "63982 <at> debbugs.gnu.org" <63982 <at> debbugs.gnu.org>
Subject: bug#63982: Shepherd can crash when a user service fails to start
Date: Sun, 25 Jun 2023 15:03:58 +0200 (CEST)

> Ludovic Courtès <ludo <at> gnu.org> hat am 22.06.2023 22:08 CEST geschrieben:
> This suggests a problem in the config file: one of the shepherd-*.scm
> files listed above ends up calling (string-append #f …).
> 
> We’d need to see those files to understand what’s happening but it looks
> different from what Maxim reported.

Indeed I misdiagnosed the issue because it happened after a guix upgrade.
I used $XDG_LOG_HOME in my shepherd services, and as of f74df2ab879fc5457982bbc85b7455a90e82317d this is no longer set by default. 
Thanks for your help!
This bug report was last modified 1 year and 364 days ago.

Previous Next

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