From: conjaroy <conjaroy@gmail.com>
To: 30939@debbugs.gnu.org
Subject: bug#30939: shepherd: detailed output should be placed into well-known location and not tty
Date: Sat, 18 Jul 2020 12:27:06 -0400 [thread overview]
Message-ID: <CABWzUjVRoB5G1u6frO09UVZQrB6BxrFD0uSvXg94dYwKKxfcFw@mail.gmail.com> (raw)
In-Reply-To: <20180325183555.cilo6qyrj43jh6he@abyayala>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
Hello -
I too have found that debugging is a challenge when a service's
stdout/stderr aren't captured automatically. From my point of view though,
the issue is not just that certain binaries lack syslog support: since a
service implementation's gexp can do much more than just exec a binary, and
since mistakes in gexps usually go unnoticed until a runtime, I've found it
easy to write scripts that trigger fatal Guile errors before the service
binary is even started (syntax errors, missing `use-modules` declarations,
etc.)
Will the solution proposed here capture output for this class of errors as
well?
[-- Attachment #2: Type: text/html, Size: 710 bytes --]
prev parent reply other threads:[~2020-07-18 16:45 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
2019-06-26 18:07 ` bug#30939: still relevant Robert Vollmert
2020-07-18 16:27 ` conjaroy [this message]
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=CABWzUjVRoB5G1u6frO09UVZQrB6BxrFD0uSvXg94dYwKKxfcFw@mail.gmail.com \
--to=conjaroy@gmail.com \
--cc=30939@debbugs.gnu.org \
/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).