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

Previous Next

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

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

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)))))))

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Andrew Wong <wongandj <at> icloud.com>
Cc: 76130-done <at> debbugs.gnu.org
Subject: Re: bug#76130: 'herd status' cannot handle inaccessible logfiles
 (shepherd 1.0.1)
Date: Sat, 08 Feb 2025 22:58:59 +0100

Hi Andrew,

Andrew Wong <wongandj <at> icloud.com> skribis:

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

Good catch.  This is fixed by cd6d35fe8adf5baaeb50adf2a96662fb30382eca,
which will be in 1.0.2, to be released in the coming days.

Thank you!

Ludo’.

Previous Next

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