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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#76130: closed ('herd status' cannot handle inaccessible
 logfiles (shepherd 1.0.1))
Date: Sat, 08 Feb 2025 22:00:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 08 Feb 2025 22:58:59 +0100
with message-id <87seooumho.fsf <at> gnu.org>
and subject line Re: bug#76130: 'herd status' cannot handle inaccessible logfiles (shepherd 1.0.1)
has caused the debbugs.gnu.org bug report #76130,
regarding 'herd status' cannot handle inaccessible logfiles (shepherd 1.0.1)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
76130: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=76130
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

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 part 3 (message/rfc822, inline)]

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.