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:

> Charlie Brady <charlieb-smarden-supervision@budge.apana.org.au> writes:
> 
> >> [ ... ]
> >
> > 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.
> 
> Thanks.
> 
> I'm already using runit, which I mentioned in my original message (that
> paragraph is quoted above).  I understand how runsvctl works in relation
> to runit.
> 
> I'm trying to figure out how to set up the "run" script in the apache
> service directory so that the "down" and "up" parameters to "runsvctrl"
> do the right things.
> 
> By "right things" I mean (for apache):
> 
>   runsvctrl up apache      =>    invoke "apachectl start"
>   runsvctrl down apache    =>    invoke "apachectl stop"

Why do you say they are the "right things"? Please re-read my previous 
message. runsv can already do what "apachectl" does, but more reliably, 
and using less resources. Why do you insist on using apachectl?

> I don't want to send a TERM signal to httpd in order to stop it, because
> I want it to shut down using the same logic that "apachectl stop" uses,
> which is definitely not to simply send a TERM signal to the httpd
> daemon.

No, that's just what "apachectl stop" does.

> To illustrate, here's an untested, quick and dirty version of the "run"
> script in the apache service directory which might do what I want:
> 
>   #!/bin/sh
> 
>   exec 2>&1
> 
>   shutdown () {
>     apachectl stop
>     exit 0
>   }
> 
>   trap "shutdown" 15
> 
>   apachectl start

Why do you want this extra shell process between runsv and apache, and why 
do you want to run apachectl?

> I'm just not sure if this is the best way to accomplish what I want
> to do.

See below:

> > 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.

You now just need a run script which does:

#! /bin/sh
exec httpd ......

with the correct args.

---
Charlie