From debbugs-submit-bounces@debbugs.gnu.org Tue Mar 27 14:59:52 2018 Received: (at 30939) by debbugs.gnu.org; 27 Mar 2018 18:59:52 +0000 Received: from localhost ([127.0.0.1]:56245 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f0tp1-0007nv-PI for submit@debbugs.gnu.org; Tue, 27 Mar 2018 14:59:51 -0400 Received: from mail.lassieur.org ([83.152.10.219]:58296) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f0toz-0007nm-Mi for 30939@debbugs.gnu.org; Tue, 27 Mar 2018 14:59:50 -0400 Received: from rodion (88.191.118.83 [88.191.118.83]) by mail.lassieur.org (OpenSMTPD) with ESMTPSA id 3a27b4bd (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO); Tue, 27 Mar 2018 18:59:47 +0000 (UTC) References: <20180325183555.cilo6qyrj43jh6he@abyayala> <87a7uvdke0.fsf@gnu.org> <20180326150859.6yf244bgjxi4oawt@abyayala> <87o9jaynpn.fsf@gnu.org> User-agent: mu4e 1.0; emacs 25.3.1 From: =?utf-8?Q?Cl=C3=A9ment?= Lassieur To: Ludovic =?utf-8?Q?Court=C3=A8s?= Subject: Re: bug#30939: shepherd: detailed output should be placed into well-known location and not tty In-reply-to: <87o9jaynpn.fsf@gnu.org> Date: Tue, 27 Mar 2018 20:59:46 +0200 Message-ID: <87370lcpjx.fsf@lassieur.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 30939 Cc: 30939@debbugs.gnu.org, ng0 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.0 (/) Ludovic Courtès writes: > Hello, > > ng0 skribis: > >> Sometimes I succeed building a system generation with an OpenSMTPD config-file >> which has syntax error that aren't picked up at configure time. When I reboot, >> 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 see >> 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 ‘journalctl’ > does. That would allow you to see the output of the daemon that failed. That would be great! > That’s the only solution I can think of. Of course we don’t have to do > that if the daemon writes error messages to syslog, but not all of them do. > > Thanks, > Ludo’.