From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#22039: [PATCH] 'guix system reconfigure' must start/restart/stop
	services
Date: Thu, 20 Sep 2018 11:47:05 +0200
Message-ID: <87efdowleu.fsf@gnu.org>
References: <874mg6rsjl.fsf@gnu.org> <87tvnhxr20.fsf@zancanaro.id.au>
	<87sh2tijb2.fsf@gnu.org> <87va7pza4p.fsf@zancanaro.id.au>
	<87tvn9b0qh.fsf@gnu.org> <87tvn8d0n7.fsf@zancanaro.id.au>
	<87lg7xh4l0.fsf@gnu.org> <871s9pfbpg.fsf@zancanaro.id.au>
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]:44512)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1g2vZ7-0001ps-Lz
	for bug-guix@gnu.org; Thu, 20 Sep 2018 05:48:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1g2vZ4-0006j5-Cs
	for bug-guix@gnu.org; Thu, 20 Sep 2018 05:48:05 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:42077)
	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 1g2vZ4-0006it-8S
	for bug-guix@gnu.org; Thu, 20 Sep 2018 05:48:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1g2vZ4-0004ij-6b
	for bug-guix@gnu.org; Thu, 20 Sep 2018 05:48:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.22039.B22039.153743685118103@debbugs.gnu.org>
In-Reply-To: <871s9pfbpg.fsf@zancanaro.id.au> (Carlo Zancanaro's message of
	"Thu, 20 Sep 2018 06:56:27 +1000")
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: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: 22039@debbugs.gnu.org

Hi,

Carlo Zancanaro <carlo@zancanaro.id.au> skribis:

> On Thu, Sep 20 2018, Ludovic Court=C3=A8s wrote:
>> Commit c4ba8c79db0aa4ba3517acc82ebafe16105fbb97 reinstates the
>> commit and removes the leftover #:replace, which was responsible for
>> the problem: ...
>
> That's great! I didn't even know about the #:replace option, so I'm
> glad you were able to find it.
>
>> If there=E2=80=99s nothing left to add to Shepherd, we can release 0.5.0
>> within a few days and then commit the Guix side of this change.
>
> This seems like the sort of thing that shouldn't have been this
> tricky. Is the exception printed somewhere? If not, then I think we
> should print the exception, or at least some information, when a
> service fails to load.

I agree.  Note that =E2=80=98herd start foo=E2=80=99 prints at least a one-=
line message
showing the exception when that happens.  The problem here is that
failure happens when =E2=80=98start=E2=80=99 is called from the shepherd co=
nfig file.
At that point there=E2=80=99s no client connected and syslogd either around
either, so presumably messages go to /dev/kmsg and/or the console.

I wouldn=E2=80=99t consider it a blocker for 0.5.0 though.  WDYT?

Thanks,
Ludo=E2=80=99.