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

Previous Next

Package: guix;

Reported by: Robert Vollmert <rob <at> vllmrt.net>

Date: Mon, 17 Jun 2019 16:43:02 UTC

Severity: important

Merged with 30939

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

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Gábor Boskovits <boskovits <at> gmail.com>
To: Robert Vollmert <rob <at> vllmrt.net>
Cc: 36264 <at> debbugs.gnu.org
Subject: bug#36264: shepherd doesn't capture service stdout/stderr
Date: Mon, 17 Jun 2019 20:49:41 +0200
[Message part 1 (text/plain, inline)]
Hello guix,

Robert Vollmert <rob <at> vllmrt.net> ezt írta (időpont: 2019. jún. 17., Hét
18:55):

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

This is also on my todo list for a while, so I can provide some additional
information. I noticed this on two services I was using:
ntp-service-type with default config and
prometheus-node-exporter-service-type with default config. I hope that
helps somewheat.


> Compare the discussion at
>
> https://lists.gnu.org/archive/html/guix-devel/2019-06/msg00186.html


Best regards,
g_bor

>
>
>
>
>
[Message part 2 (text/html, inline)]

This bug report was last modified 252 days ago.

Previous Next


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