unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 26 Mar 2018 15:41:27 +0200	[thread overview]
Message-ID: <87a7uvdke0.fsf@gnu.org> (raw)
In-Reply-To: <20180325183555.cilo6qyrj43jh6he@abyayala> (ng0@n0.is's message of "Sun, 25 Mar 2018 18:35:55 +0000")

Hi ng0,

ng0 <ng0@n0.is> skribis:

> Problem, not just when a service is misbehaving after successful system reconfigure:
>
> $ sudo herd start smtpd
> Password: 
> Service smtpd could not be started.
> herd: failed to start service smtpd
>
>
>
> This is on virtual terminal in X11, as well as in /var/log/messages,
> /var/log/shepherd.log, etc.
> This is not enough. If I wanted more info, I'd expect that
> sudo herd status smtpd would give it (which it does not), so the only
> reliable source of information so far is tty 1. Can we fix that in
> one of the next shepherd releases? Or is this something we have to
> fix in Guix?

So you’re saying that you’d like shepherd to show more info as to why
the service could not be started, right?

Thanks,
Ludo’.

  reply	other threads:[~2018-03-26 13:42 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 [this message]
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 ` 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=87a7uvdke0.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).