From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [shepherd] herd status suggestion
Date: Sun, 10 Jun 2018 21:39:05 +0200 [thread overview]
Message-ID: <874liae8iu.fsf@gnu.org> (raw)
In-Reply-To: <20180610143153.juzeulj2cruytwsc@abyayala> (Nils Gillmann's message of "Sun, 10 Jun 2018 14:31:53 +0000")
Hello Nils,
Nils Gillmann <ng0@n0.is> skribis:
> Ricardo Wurmus transcribed 982 bytes:
>>
>> Hi Nils,
>>
>> > abyayala$ sudo herd status tor
>> > Status of tor:
>> > It is stopped.
>> > It is disabled.
>> > Provides (tor).
>> > Requires (user-processes loopback syslogd).
>> > Conflicts with ().
>> > Will be respawned.
>> > Last respawned on Sun Jun 10 08:08:45Z 2018.
>> >
>> >
>> > Would it be an option to change the status output to,
>> > if it conflicts with no other service:
>> >
>> > Conflicts with no other services.
>> >
>> > instead of the representation of an empty list?
[...]
> Related and similar: Would it be reasonable to change the output from list-style,
> like:
> Depends on: (foo bar irks boot)
>
> to the probably tiny bit better readable:
>
> Depends on: foo, bar, irks, boot
>
> for humans?
I agree with both proposals. :-)
The output of ‘herd status’ is meant for humans to read, not for
machines to process, so it makes sense to make these changes IMO. For
machines there’s a well-defined protocol that can be used, so we should
do our best to make ‘herd status’ useful to humans.
If you want to give it a try, this is all happening in
modules/shepherd/scripts/herd.scm.
Thank you,
Ludo’.
next prev parent reply other threads:[~2018-06-10 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 10:34 [shepherd] herd status suggestion Nils Gillmann
2018-06-10 11:31 ` Ricardo Wurmus
2018-06-10 14:31 ` Nils Gillmann
2018-06-10 19:39 ` Ludovic Courtès [this message]
2018-06-10 19:47 ` Nils Gillmann
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874liae8iu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).