From: Charlie Brady <charlieb-smarden-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: Who actually gets the TERM signal in "runsvctrl down"?
Date: Fri, 25 Jun 2004 15:48:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0406251544170.11857-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <m3eko3e9iy.fsf@asfast.com>
On Fri, 25 Jun 2004, Lloyd Zusman wrote:
> It also documents that the signals will work. But I want to use the
> command line options, in case some future version of apache kills the
> daemons in a different way, or perhaps does some cleanup before sending
> the signal.
If you try to solve problems you don't already know that people have, you
create unnecessary complexity. Always start with the simplest possible
program.
Russell Nelson
Parts that don't exist can't break.
Russell Nelson
> > In that case why use runit at all?
>
> Because I want the apache daemon to automatically be restarted in case
> it dies.
So restart it in the simplest and most reliable way possible.
> For now, I'll take my chances with "httpd -k stop".
You can lead a horse to water ....
---
Charlie
next prev parent reply other threads:[~2004-06-25 19:48 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
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 [this message]
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=Pine.LNX.4.44.0406251544170.11857-100000@e-smith.charlieb.ott.istop.com \
--to=charlieb-smarden-supervision@budge.apana.org.au \
--cc=supervision@list.skarnet.org \
/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).