Re: Customised control help

[Charlie Brady <charlieb-supervision@budge.apana.org.au>]

On Tue, 1 Jan 2008, Rehan Khan wrote:

> From the man page for runsv:
>
> Customize Control
> For each control character c sent to the control pipe, runsv first checks if
...
> I have a couple of questions:
>
> 1) are all the control codes supported? Not just the ones in the above
> paragraph? (h, 1, 2, etc)

Yes, that's what the "for each" means :-)

> 2) I have the t script for some of my services. Do I have to send a term
> manually after I have run the pre-term commands I need (i.e do I have to do
> everything a term signal should do?)?

If your custom control script exits non-zero, then runsv will send the 
term signal. If your custom script exits zero, runsv will do nothing. You 
therefore have two choices for sending the term signal - do it yourself in 
the custom script, or allow runsv to do it by exiting non-zero.

> Right now the services don't stop properly and the status command 
> reports 'run, want down' and the service stays up without exiting.

So you have to fix the service, or do something other than send a term 
signal to terminate the service.

> 4) Is there a more detailed description of customised control somewhere?

I think the man page of runsv is complete and accurate. What do you think 
is missing? The source code might help you if you wish to learn more or to 
confirm what you read in the man page.