Re: runit - access to run script's exit status for finish?

[Gerrit Pape <pape@smarden.org>]

On Mon, Aug 29, 2005 at 05:08:16AM -0500, Charles Duffy wrote:
> 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>
> ...

I would prefer not to change the current output of 'sv 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.

This I like.  Instead of command line switches to the status command, we
could also use specific commands, such as
 $ sv status-pid <service1> <service2>
 <pid-service1>
 <pid-service2>
 $ sv status-uptime <service1>
 <number-of-seconds-for-service1>
 $ 
 ...
 
> 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.

Jup, thanks, Gerrit.