From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30939@debbugs.gnu.org, ng0 <ng0@n0.is>
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 [thread overview]
Message-ID: <87fu4l1dkv.fsf@netris.org> (raw)
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")
ludo@gnu.org (Ludovic Courtès) writes:
> 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.
This would be very helpful.
Mark
next prev parent reply other threads:[~2018-03-27 20:15 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
2018-03-27 9:15 ` ng0
2018-03-27 18:59 ` Clément Lassieur
2018-03-27 20:13 ` Mark H Weaver [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu4l1dkv.fsf@netris.org \
--to=mhw@netris.org \
--cc=30939@debbugs.gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.