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

[Charles Duffy <cduffy@spamcop.net>]

On Sat, 27 Aug 2005 19:24:35 +0000, Gerrit Pape wrote:

> I still don't know what's the best way to pass this information to the
> ./finish script.  Providing the exit code of ./run through the
> environment seems to be the best solution, but (1) only the ./finish
> script's environment should be altered, not the ./run script's, and (2)
> runsv currently doesn't allocate memory dynamically, I don't want to
> change that.

Hmm.

I suppose doing an unsetenv() is unacceptable because it would interfere
wih run's environment if run had set (or was expecting the outside world
to set) a variable with the same name. Personally, to be honest, I'd
consider this acceptable so long as it was documented and the chosen name
was unlikely to collide with anything -- but even so, I can appreciate our
reluctance to go this route.

Your suggestion of stuffing it in the status file makes sense, then -- but
a convenient way to get the info still out is still needed. How about
having an argument to runsvstat to retrieve *only* this piece of
information? (For that matter, being able to do the same with other data
in the status file would be likewise useful).