From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: [herd] Have status display services as a bulleted list.
Date: Sat, 26 Nov 2016 00:08:59 +0100
Message-ID: <87y407p378.fsf@gnu.org>
References: <87oa15j4cq.fsf@dustycloud.org> <87shqg4zvx.fsf@gnu.org>
	<87h96wi2fn.fsf@dustycloud.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33264)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cAPc9-0007Mf-LK
	for guix-devel@gnu.org; Fri, 25 Nov 2016 18:09:06 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cAPc6-00085b-F6
	for guix-devel@gnu.org; Fri, 25 Nov 2016 18:09:05 -0500
In-Reply-To: <87h96wi2fn.fsf@dustycloud.org> (Christopher Allan Webber's
	message of "Thu, 24 Nov 2016 22:55:08 -0600")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org

Christopher Allan Webber <cwebber@dustycloud.org> skribis:

> Ludovic Court=C3=A8s writes:
>
>> Christopher Allan Webber <cwebber@dustycloud.org> skribis:
>>
>>> I don't know about you, but I am totally unable to read the
>>> "herd status" line as it exists in the current state.  I mean, I love
>>> sexps, but even I don't like a completely flat and ungreppable list
>>> printed to stdout.
>>
>> Agreed!
>>
>>> *** New output ***
>>>
>>> cwebber@oolong:~/devel/shepherd$ sudo ./herd -s /var/run/shepherd/socke=
t status
>>> Started:
>>>  + file-system-/run/systemd
>>>  + xorg-server
>>>  + file-system-/sys/fs/cgroup/cpuacct
>>>  + file-system-/mnt/debian
>>>  + syslogd
>>>  + term-tty1
>>>  + root-file-system
>>>  + file-system-/sys/fs/cgroup/blkio
>>>  + avahi-daemon
>>
>> Works for me!  I=E2=80=99m just wondering if there are ideas we could/sh=
ould
>> follow more closely the output of =E2=80=98systemctl status=E2=80=99.  I=
IRC, it displays
>> a couple of lines for each service; for instance, we could display the
>> =E2=80=9Crunning=E2=80=9D value and dependencies of each service, indent=
ed below its
>> name.
>>
>> WDYT?  Would that make sense?
>>
>> Ludo=E2=80=99.
>
> It's a good idea, and I think we should shoot for better output.
> Listing a tree of dependencies is a great idea.
>
> But I'm unlikely to have time to get to it soon.  I think it should be
> on our TODO list, but for now, the preceding patch will still be a nice
> improvement.

You=E2=80=99re right.  Applied with an adjusted test.

Thank you!

Ludo=E2=80=99.