Customised control help

[Rehan Khan <rehan.khan@dsl.pipex.com>]

Hi

From the man page for runsv:

Customize Control
 For each control character c sent to the control pipe, runsv first checks if 
service/control/c exists and is executable. If so, it starts service/control/c 
and waits for it to terminate, before interpreting the command. If the program 
exits with return code 0, runsv refrains from sending the service the 
corresponding signal. The command o is always considered as command u. On 
command d first service/control/t is checked, and then service/control/d. On 
command x first service/control/t is checked, and then service/control/x. The 
control of the optional log service cannot be customized.

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)

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?)? Right now the services don't stop 
properly and the status command reports 'run, want down' and the service stays 
up without exiting.

3) (Not directly related to the above.). I have a service called bluetooth 
which starts up the hcid process. The normal fedora init script runs some 
commands after the hcid daemon starts (using hciattach command). If the 
service starts successfully how can I run these post start commands within the 
runit method instead of in a separate script. I would like to keep everything 
a service does in the service directory. (I could background and disown 
another script with a sleep pre-pended but this is not a particularly clean 
implementation)

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

Thanks in advance
R