From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
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
Message-ID: <87a7uvdke0.fsf@gnu.org>
References: <20180325183555.cilo6qyrj43jh6he@abyayala>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58818)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1f0SNy-00031p-5Z
	for bug-guix@gnu.org; Mon, 26 Mar 2018 09:42:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1f0SNu-0001ab-5x
	for bug-guix@gnu.org; Mon, 26 Mar 2018 09:42:06 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:45860)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1f0SNu-0001aR-1f
	for bug-guix@gnu.org; Mon, 26 Mar 2018 09:42:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1f0SNt-0006tf-Qi
	for bug-guix@gnu.org; Mon, 26 Mar 2018 09:42:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.30939.B30939.152207169126471@debbugs.gnu.org>
In-Reply-To: <20180325183555.cilo6qyrj43jh6he@abyayala> (ng0@n0.is's message
	of "Sun, 25 Mar 2018 18:35:55 +0000")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: ng0 <ng0@n0.is>
Cc: 30939@debbugs.gnu.org

Hi ng0,

ng0 <ng0@n0.is> skribis:

> Problem, not just when a service is misbehaving after successful system r=
econfigure:
>
> $ sudo herd start smtpd
> Password:=20
> 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=E2=80=99re saying that you=E2=80=99d like shepherd to show more info=
 as to why
the service could not be started, right?

Thanks,
Ludo=E2=80=99.