bug#30939: closed (shepherd: detailed output should be placed into well-known location and not tty)

[GNU bug Tracking System]

Your message dated Fri, 06 Sep 2024 09:18:41 +0200
with message-id <87ed5x45da.fsf@gnu.org>
and subject line Re: bug#36264: shepherd doesn't capture service stdout/stderr
has caused the debbugs.gnu.org bug report #36264,
regarding shepherd: detailed output should be placed into well-known location 
and not tty
to be marked as done.

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


-- 
36264: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36264
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> shepherd: detailed output should be placed into well-known location and not tty
>
>
>
>
> Date: 
>
> Sun, 25 Mar 2018 18:35:55 +0000
>
>
>
>
> Problem, not just when a service is misbehaving after successful system 
> reconfigure:
>
> $ sudo herd start smtpd
> Password: 
> Service smtpd could not be started.
> herd: failed to start service smtpd
>
>
>
> This is on virtual terminal in X11, as well as in /var/log/messages,
> /var/log/shepherd.log, etc.
> This is not enough. If I wanted more info, I'd expect that
> sudo herd status smtpd would give it (which it does not), so the only
> reliable source of information so far is tty 1. Can we fix that in
> one of the next shepherd releases? Or is this something we have to
> fix in Guix?
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#36264: shepherd doesn't capture service stdout/stderr
>
>
>
>
> Date: 
>
> Fri, 06 Sep 2024 09:18:41 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13)
>
>
>
>
> Robert Vollmert <rob@vllmrt.net> skribis:
>
> > On a pretty fresh Guix System install, I see some regular
> > sshd error messages on tty1 (which I guess means they’re
> > written to /dev/console). Also, setting up a regular
> > shepherd service via make-forkexec-constructor for a
> > program that logs to stderr (postgrest which I’m in the
> > process of packaging), all output goes to tty1.
> >
> > Compare the discussion at
> >
> > https://lists.gnu.org/archive/html/guix-devel/2019-06/msg00186.html
>
> Fortunately that was fixed in Shepherd 0.9.0 (April 2022).
>
> Ludo’.
>
>
> --- End Message ---