From: Jim Zajkowski <jim@jimz.net>
Subject: Re: Who actually gets the TERM signal in "runsvctrl down"?
Date: Fri, 25 Jun 2004 14:40:12 -0400 [thread overview]
Message-ID: <17BAEA9A-C6D7-11D8-A5AC-000A95DA58FE@jimz.net> (raw)
In-Reply-To: <m38yebiq0u.fsf@asfast.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jun 25, 2004, at 12:03 PM, Lloyd Zusman wrote:
> 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.
From httpd (1.3.29) -h:
-F: run main process in foreground, for process supervisors
From the httpd manpage:
To stop it, send a TERM signal to the initial (parent) process.
httpd is designed to run directly under daemontools / runit using the
- -F parameter to prevent it from detaching and running in the
background. What that means: you don't need to, or really should, use
apachectl.
> #!/bin/sh
> [...]
> apachectl start
Great: apachectl start returns while httpd runs in the background,
which means daemontools / runit will run your script again, and again.
You'll need to sleep endlessly.
I run a bunch of webservers all using daemontools control of httpd
directly. Works well and is highly reliable.
It seems to me you are missing the fundamental technique that
daemontools / runit is based around. This is like trying to use dd as
a text editor.
- --Jim
- - - -
Jim Zajkowski OpenPGP 0x21135C3 http://www.jimz.net/pgp.asc
System Administrator 8A9E 1DDF 944D 83C3 AEAB 8F74 8697 A823 2113 5C53
UM Life Sciences Institute
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFA3HGMhpeoIyETXFMRAsyOAKCHh+JpN9k/yBf3tF8n77e/yyu11QCcDlvS
G8YlRWBu17q0JJqjjGmEXLE=
=T214
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-25 18:40 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
2004-06-26 3:49 ` Paul Jarc
2004-06-26 21:10 ` Lloyd Zusman
2004-06-25 18:40 ` Jim Zajkowski [this message]
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=17BAEA9A-C6D7-11D8-A5AC-000A95DA58FE@jimz.net \
--to=jim@jimz.net \
/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).