supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charles Duffy <cduffy@spamcop.net>
Subject: Re: runit - access to run script's exit status for finish?
Date: Mon, 29 Aug 2005 05:08:16 -0500	[thread overview]
Message-ID: <deums1$2t9$1@sea.gmane.org> (raw)
In-Reply-To: <20050829080807.24479.qmail@b57f7a37a4464e.315fe32.mid.smarden.org>

Gerrit Pape wrote:
> To query this information, I would prefer to extend the sv program, not
> runsvstat.  runsvctrl, runsvstat, svwaitdown, svwaitup, most probably
> will get obsolete some time, as the functionality is integrated into sv.
> I'm not sure about the user interface, whether sv should support special
> commands for this, or command line switches, or so.

How about a subcommand with switches? Something like:

$ sv status <service1> <service2> ...
service1 STATUS (up|down|...)
service1 TIME <number-of-seconds>
service1 LASTEXIT <last run command's exit status>
service2 STATUS (up|down|...)
service2 TIME <number-of-seconds>
service2 LASTEXIT <last run command's exit status>
...

$ sv status -s <service1> <service2> ...
<state-of-service1>
<state-of-service2>

$ sv status -t <service1> <service2> ...
<number-of-seconds-for-service1>
<number-of-seconds-for-service2>

$ sv status -e <service1> <service2> ...
<last run command's exit status for service1>
<last run command's exit status for service2>

and so forth.

The full "sv status" output is trivially handlable with gawk, whereas 
the specific items (selectable w/ a flag) don't require even that, 
particularly if there's only one service named.



  reply	other threads:[~2005-08-29 10:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 16:26 Charles Duffy
2005-05-29  5:52 ` Gerrit Pape
2005-05-30  7:42   ` Laurent Bercot
2005-05-31 11:49     ` Gerrit Pape
2005-05-31 14:28       ` Paul Jarc
2005-05-31 19:09         ` Gerrit Pape
2005-06-01  0:05           ` Joan Picanyol i Puig
2005-08-26 20:30             ` Charles Duffy
2005-08-27 19:24               ` Gerrit Pape
2005-08-27 22:56                 ` Charles Duffy
2005-08-29  8:12                   ` Gerrit Pape
2005-08-29 10:08                     ` Charles Duffy [this message]
2005-08-30 11:06                       ` Gerrit Pape
2005-08-30 16:55                         ` Charles Duffy
2005-09-01  9:13                           ` Gerrit Pape
2005-09-12 15:11                     ` Charles Duffy
2005-09-15  9:33                       ` Gerrit Pape
2005-09-15 12:18                         ` Paul Jarc
2005-09-15 14:46                           ` Gerrit Pape
2005-09-15 18:10                             ` Charles Duffy
2005-09-16  8:15                               ` Gerrit Pape
2005-08-27 23:01                 ` Charles Duffy

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='deums1$2t9$1@sea.gmane.org' \
    --to=cduffy@spamcop.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.
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 NNTP newsgroup(s).