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

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

On Sat, 26 Jun 2004, Lloyd Zusman wrote:

> Lloyd Zusman <ljz@asfast.com> writes:
> 
> > [ ... ]
> >
> >   restart:   runscvtrl t apache; runsvctrl u apache
> >   (causes cleanup stuff to run during the second command)
> 
> We both suggested this one, but I have a question:
> 
> Why do we need the second "u" command?  Won't the "run" script restart
> on its own after the "t" command, thereby obviating the need for the "u"
> command?  In this case, the cleanup stuff in the script will get
> re-invoked on restart, correct?

Please re-read previous messages (carefully) if something isn't clear. 
This was answered earlier.

To answer your questions - yes to both. But ..

"apachectl restart" will start apache if it is not already running. One of 
the "runsvctrl t" and "runsvctl u" will have no effect during restart - 
but you need to know whether apache is already running to know which one.

The order of "t" and "u" is significant (as is "1" and "u" for 
"graceful"). If you do them in the opposite order, you may hit apache with 
signals during startup, which might result in unexpected behaviour.

---
Charlie