Re: Who actually gets the TERM signal in "runsvctrl down"?

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

On Fri, 25 Jun 2004, Lloyd Zusman wrote:

> Who actually receives the TERM signal when "runsvctrl down SVC" is
> invoked?  Does that signal get sent to the SVC/run script?

Correct. Or more correctly, the inheritor of that process, presumably an 
apache instance started by exec.

> The reason I'm asking is that I'm trying to put apache under runit
> control.  I'd like "runsvctrl up apache" to invoke "apachectl start"
> (that's trivially easy), and I'd like "runsvctrl down apache" to invoke
> "apachectl stop".
> 
> If the TERM signal gets sent to the SVC/run script, then I can write a
> trap for that signal within that script which would cause
> "apachectl stop" to be invoked, thereby providing a clean shutdown.
> 
> Or is there a better way to do this?

The better way is runit/daemontools. runsvctrl is just a shell script 
which tries to do what runsv is already able to do reliably. It delivers a 
signal to the session leading httpd process, which it has hopefully found 
by way of a pid file. That process then "does the right thing" with its 
children.

For "apachectl stop", just do "runsvctrl down apache". For "apachectl 
graceful", do "runsvctrl 1 apache; raunsvctrl u apache". For "apachectrl 
restart", do "runsvctrl t apache; raunsvctrl u apache". Etc.

---
Charlie