From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@n0.is>
Cc: 30939@debbugs.gnu.org
Subject: bug#30939: shepherd: detailed output should be placed into well-known location and not tty
Date: Tue, 27 Mar 2018 09:36:20 +0200 [thread overview]
Message-ID: <87o9jaynpn.fsf@gnu.org> (raw)
In-Reply-To: <20180326150859.6yf244bgjxi4oawt@abyayala> (ng0@n0.is's message of "Mon, 26 Mar 2018 15:10:36 +0000")
Hello,
ng0 <ng0@n0.is> 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’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’.
next prev parent reply other threads:[~2018-03-27 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 18:35 bug#30939: shepherd: detailed output should be placed into well-known location and not tty ng0
2018-03-26 13:41 ` Ludovic Courtès
2018-03-26 15:10 ` ng0
2018-03-27 7:36 ` Ludovic Courtès [this message]
2018-03-27 9:15 ` ng0
2018-03-27 18:59 ` Clément Lassieur
2018-03-27 20:13 ` Mark H Weaver
2019-06-26 18:07 ` bug#30939: still relevant Robert Vollmert
2020-07-18 16:27 ` bug#30939: shepherd: detailed output should be placed into well-known location and not tty conjaroy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9jaynpn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30939@debbugs.gnu.org \
--cc=ng0@n0.is \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).