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 23:01:13 -0400 [thread overview]
Message-ID: <m3k6xvaupy.fsf@asfast.com> (raw)
In-Reply-To: <m3d63ndon7.fsf@asfast.com>
I just answered my own question. See below ...
Lloyd Zusman <ljz@asfast.com> writes:
> Charlie Brady <charlieb-smarden-supervision@budge.apana.org.au> writes:
>
>> On Fri, 25 Jun 2004, Lloyd Zusman wrote:
>>
>> [ ... ]
>>
>> Being started and being restarted are both covered by what is done in the
>> run script. If you need something special done when you stop a daemon
>> (which usually is not the case), then with runit you can provide a
>> "finish" script.
>
> But look more carefully at the script fragment I wrote in the previous
> message: I want to do something different between "restart" and
> "graceful" ...
>
> restart: before sending the signal to httpd, clean up some
> subdirectories under /tmp that are used in certain web apps
> on my site; and only _then_ send the signal to httpd (do
> this before "start", also, but that's a trivial case)
>
> graceful: just send the signal to httpd and _do_ _not_ clean up any
> directories, because in apache, a "graceful" restart keeps
> connections open, etc., and I don't want existing
> data to be lost
>
> How do I cause my /tmp directories to get cleaned up during "restart",
> but not during "graceful"?
Hmm ... maybe I can do it this way (almost the same as what you had
suggested, but with a slight difference for "graceful") ...
Use something akin to your suggested "run" script ...
#! /bin/sh
exec 2>&1
do_your_cleanup_stuff
TZ=xxxxx exec chpst -P /usr/sbin/httpd -DNO_DETACH
Then ...
start: runsvctrl u apache
(causes cleanup stuff to run)
stop: runsvctrl d apache
(no cleanup stuff gets run)
graceful: runsvctrl 1 apache
(no cleanup stuff gets run)
restart: runscvtrl t apache; runsvctrl u apache
(causes cleanup stuff to run during the second command)
--
Lloyd Zusman
ljz@asfast.com
God bless you.
next prev parent reply other threads:[~2004-06-26 3:01 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
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 [this message]
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=m3k6xvaupy.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).