From: Lloyd Zusman <ljz@asfast.com>
Cc: Charlie Brady <charlieb-smarden-supervision@budge.apana.org.au>
Subject: Re: Who actually gets the TERM signal in "runsvctrl down"?
Date: Fri, 25 Jun 2004 12:03:13 -0400 [thread overview]
Message-ID: <m38yebiq0u.fsf@asfast.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0406251029110.11857-100000@e-smith.charlieb.ott.istop.com>
Charlie Brady <charlieb-smarden-supervision@budge.apana.org.au> writes:
> On Fri, 25 Jun 2004, Lloyd Zusman wrote:
>>
>> [ ... ]
>>
>> 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".
>>
>> [ ... ]
>
> 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"
[ actually, I already know how to do an "up" ... it's the "down"
that I have a question about ]
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.
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
I'm just not sure if this is the best way to accomplish what I want
to do.
> 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.
--
Lloyd Zusman
ljz@asfast.com
God bless you.
next prev parent reply other threads:[~2004-06-25 16:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 14:01 Lloyd Zusman
2004-06-25 15:33 ` Charlie Brady
2004-06-25 16:03 ` Lloyd Zusman [this message]
2004-06-25 16:11 ` Charlie Brady
2004-06-25 16:36 ` Lloyd Zusman
2004-06-25 17:15 ` Paul Jarc
2004-06-26 0:26 ` Scott Gifford
2004-06-26 1:39 ` Lloyd Zusman
2004-06-26 2:17 ` Charlie Brady
2004-06-26 2:44 ` Lloyd Zusman
2004-06-26 3:01 ` Lloyd Zusman
2004-06-26 4:03 ` Lloyd Zusman
2004-06-26 8:17 ` Thomas Schwinge
2004-06-26 15:45 ` Charlie Brady
2004-06-25 18:27 ` Charlie Brady
2004-06-25 19:13 ` Lloyd Zusman
2004-06-25 19:48 ` Charlie Brady
2004-06-26 3:49 ` Paul Jarc
2004-06-26 21:10 ` Lloyd Zusman
2004-06-25 18:40 ` Jim Zajkowski
2004-06-25 16:13 ` Dean Hall
2004-06-25 16:17 ` Charlie Brady
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38yebiq0u.fsf@asfast.com \
--to=ljz@asfast.com \
--cc=charlieb-smarden-supervision@budge.apana.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).