unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
* bug#36264: shepherd doesn't capture service stdout/stderr
@ 2019-06-17 16:41 Robert Vollmert
  2019-06-17 18:49 ` Gábor Boskovits
  2024-09-06  7:18 ` Ludovic Courtès
  0 siblings, 2 replies; 3+ messages in thread
From: Robert Vollmert @ 2019-06-17 16:41 UTC (permalink / raw)
  To: 36264

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#36264: shepherd doesn't capture service stdout/stderr
  2019-06-17 16:41 bug#36264: shepherd doesn't capture service stdout/stderr Robert Vollmert
@ 2019-06-17 18:49 ` Gábor Boskovits
  2024-09-06  7:18 ` Ludovic Courtès
  1 sibling, 0 replies; 3+ messages in thread
From: Gábor Boskovits @ 2019-06-17 18:49 UTC (permalink / raw)
  To: Robert Vollmert; +Cc: 36264

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

Hello guix,

Robert Vollmert <rob@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

>
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1837 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#36264: shepherd doesn't capture service stdout/stderr
  2019-06-17 16:41 bug#36264: shepherd doesn't capture service stdout/stderr Robert Vollmert
  2019-06-17 18:49 ` Gábor Boskovits
@ 2024-09-06  7:18 ` Ludovic Courtès
  1 sibling, 0 replies; 3+ messages in thread
From: Ludovic Courtès @ 2024-09-06  7:18 UTC (permalink / raw)
  To: 36264-done

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




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-09-06  7:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-17 16:41 bug#36264: shepherd doesn't capture service stdout/stderr Robert Vollmert
2019-06-17 18:49 ` Gábor Boskovits
2024-09-06  7:18 ` Ludovic Courtès

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).