GNU bug report logs - #36264
shepherd doesn't capture service stdout/stderr

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#36264: closed (shepherd doesn't capture service stdout/stderr)
Date: Fri, 06 Sep 2024 07:20:02 +0000

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

Your message dated Fri, 06 Sep 2024 09:18:41 +0200
with message-id <87ed5x45da.fsf <at> 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 doesn't capture service stdout/stderr
to be marked as done.

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


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

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

From: Robert Vollmert <rob <at> vllmrt.net>
To: bug-guix <at> gnu.org
Subject: shepherd doesn't capture service stdout/stderr
Date: Mon, 17 Jun 2019 18:41:37 +0200

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

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: 36264-done <at> debbugs.gnu.org
Subject: Re: bug#36264: shepherd doesn't capture service stdout/stderr
Date: Fri, 06 Sep 2024 09:18:41 +0200

Robert Vollmert <rob <at> 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’.

Previous Next

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