From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor?= Boskovits Subject: bug#36264: shepherd doesn't capture service stdout/stderr Date: Mon, 17 Jun 2019 20:49:41 +0200 Message-ID: References: <60AB29DA-9E60-4C78-B1C8-7BAD9318D69F@vllmrt.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000003773df058b8976cf" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:41119) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hcwig-0003XF-HV for bug-guix@gnu.org; Mon, 17 Jun 2019 14:51:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hcwie-0000mx-EI for bug-guix@gnu.org; Mon, 17 Jun 2019 14:51:06 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:58008) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hcwic-0000ky-0L for bug-guix@gnu.org; Mon, 17 Jun 2019 14:51:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hcwib-0007rC-Or for bug-guix@gnu.org; Mon, 17 Jun 2019 14:51:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <60AB29DA-9E60-4C78-B1C8-7BAD9318D69F@vllmrt.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Robert Vollmert Cc: 36264@debbugs.gnu.org --0000000000003773df058b8976cf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello guix, Robert Vollmert ezt =C3=ADrta (id=C5=91pont: 2019. j=C3=BA= n. 17., H=C3=A9t 18:55): > On a pretty fresh Guix System install, I see some regular > sshd error messages on tty1 (which I guess means they=E2=80=99re > 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=E2=80=99m 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 > > > > > --0000000000003773df058b8976cf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello guix,

Robert Vol= lmert <rob@vllmrt.net> ezt =C3= =ADrta (id=C5=91pont: 2019. j=C3=BAn. 17., H=C3=A9t 18:55):
On a pretty fresh Guix System install, I see some = regular
sshd error messages on tty1 (which I guess means they=E2=80=99re
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=E2=80=99m 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 d= efault config and
prometheus-node-exporter-service-t= ype with default config. I hope that helps somewheat.

<= div dir=3D"auto">
Best regards,
g_bor




--0000000000003773df058b8976cf--