GNU bug report logs - #76130
'herd status' cannot handle inaccessible logfiles (shepherd 1.0.1)

Previous Next

Package: guix;

Reported by: Andrew Wong <wongandj <at> icloud.com>

Date: Fri, 7 Feb 2025 20:30:02 UTC

Severity: normal

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

Bug is archived. No further changes may be made.

Full log


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

From: Andrew Wong <wongandj <at> icloud.com>
To: bug-guix <at> gnu.org
Subject: 'herd status' cannot handle inaccessible logfiles (shepherd 1.0.1)
Date: Fri, 7 Feb 2025 15:29:25 -0500
Hello,

I've found a bug in shepherd 1.0.1. When a service has a log file in an 
'inaccessible' location, e.g. a home service logging to /var/log, it 
causes 'herd status $service' to hang, as well as the overall 'herd 
service' command. I found it with this service[1] which silently failed 
to log, I guess, until I updated shepherd and found this bug.

[1]:

(service home-shepherd-service-type
        (home-shepherd-configuration
         (services
          (list
           (shepherd-service
        (provision '(emacs))
        (start #~(make-forkexec-constructor
              (list #$(file-append emacs-pgtk-xwidgets "/bin/emacs")
                "--fg-daemon")
              #:log-file "/var/log/emacs.log"))
        (stop #~(make-kill-destructor)))))))





This bug report was last modified 104 days ago.

Previous Next


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