From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#30939: shepherd: detailed output should be placed into well-known location and not tty Date: Tue, 27 Mar 2018 16:13:52 -0400 Message-ID: <87fu4l1dkv.fsf@netris.org> References: <20180325183555.cilo6qyrj43jh6he@abyayala> <87a7uvdke0.fsf@gnu.org> <20180326150859.6yf244bgjxi4oawt@abyayala> <87o9jaynpn.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49597) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f0uzp-0005SY-4F for bug-guix@gnu.org; Tue, 27 Mar 2018 16:15:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f0uzm-000693-0d for bug-guix@gnu.org; Tue, 27 Mar 2018 16:15:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:48381) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f0uzl-00068s-TB for bug-guix@gnu.org; Tue, 27 Mar 2018 16:15:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1f0uzl-00019f-KO for bug-guix@gnu.org; Tue, 27 Mar 2018 16:15:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87o9jaynpn.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 27 Mar 2018 09:36:20 +0200") 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 30939@debbugs.gnu.org, ng0 ludo@gnu.org (Ludovic Court=C3=A8s) writes: > ng0 skribis: > >> Sometimes I succeed building a system generation with an OpenSMTPD confi= g-file >> which has syntax error that aren't picked up at configure time. When I r= eboot, >> not being aware of this, I have to switch to tty to read the reasons why= it >> crashed. >> Because this is a desktop system, I have to start the service again to s= ee >> the error output directly from the daemon. > > I think shepherd could capture stdout/stderr of the processes it starts > and make it available, in a way similar in spirit to what =E2=80=98journa= lctl=E2=80=99 > does. That would allow you to see the output of the daemon that failed. This would be very helpful. Mark