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

[Charles Duffy <cduffy@spamcop.net>]

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

Yes, that'd work too. My instinct would be to use flags if we have a 
particularly large number of items that could be queried, or subcommands 
if it's going to remain a fairly small set.

Right now we've got:
- PID
- uptime
- current state
- desired state
- last exit status
...anything I'm missing?

Five is a small enough number to be reasonable -- I'm just a bit leery 
after GNU Arch (where one of the constant complaints from new users was 
the sheer number of subcommands).

It's your baby, though, and if I'm going to be writing a patch, my 
intent is for it to meet your standards.