all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Allan Webber <cwebber@dustycloud.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [herd] Have status display services as a bulleted list.
Date: Thu, 24 Nov 2016 22:55:08 -0600	[thread overview]
Message-ID: <87h96wi2fn.fsf@dustycloud.org> (raw)
In-Reply-To: <87shqg4zvx.fsf@gnu.org>

Ludovic Courtès 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/socket 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’m just wondering if there are ideas we could/should
> follow more closely the output of ‘systemctl status’.  IIRC, it displays
> a couple of lines for each service; for instance, we could display the
> “running” value and dependencies of each service, indented below its
> name.
>
> WDYT?  Would that make sense?
>
> Ludo’.

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.

If someone else wants to step up to make those changes, of course,
great!

 - Chris

  reply	other threads:[~2016-11-25  4:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 21:03 [herd] Have status display services as a bulleted list Christopher Allan Webber
2016-11-24  8:28 ` Hartmut Goebel
2016-11-24  9:00   ` Alex Sassmannshausen
2016-11-24 16:16 ` Ludovic Courtès
2016-11-25  4:55   ` Christopher Allan Webber [this message]
2016-11-25 23:08     ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h96wi2fn.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.