[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#30939: shepherd: detailed output should be placed into well-known lo
bug#30939: shepherd: detailed output should be placed into well-known location and not tty
Mon, 26 Mar 2018 15:41:27 +0200
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
ng0 <address@hidden> skribis:
> Problem, not just when a service is misbehaving after successful system
> $ sudo herd start smtpd
> 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?