shepherd doesn't capture service stdout/stderr

Robert Vollmert wrote on 17 Jun 2019 18:41

Recipients:(address . bug-guix@gnu.org)

Message-ID:60AB29DA-9E60-4C78-B1C8-7BAD9318D69F@vllmrt.net

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

Gábor Boskovits wrote on 17 Jun 2019 20:49

Recipients:(name . Robert Vollmert)(address . rob@vllmrt.net)(address . 36264@debbugs.gnu.org)

Message-ID:CAE4v=piqPrAZHxbf90JO__SCC4+sRiV1apXd7ZQFAB_FD49gSg@mail.gmail.com

Hello guix,

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

18:55):

Toggle quote (8 lines)

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

Toggle quote (5 lines)

> Compare the discussion at

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

Best regards,

g_bor

Toggle quote (5 lines)>
>
>
>
>

Attachment: file

Brice Waegeneire wrote on 5 Apr 2020 16:28

merge 36264 30939

Recipients:(address . control@debbugs.gnu.org)

Message-ID:10441295b633fc99948b7eed4aad51f3@waegenei.re

severity 36264 important
merge 36264 30939
quit

Your comment

Commenting via the web interface is currently disabled.