From: Thomas Schwinge <schwinge-lists-skarnet.org-supervision@nic-nac-project.de>
Cc: supervision@list.skarnet.org
Subject: Re: Who actually gets the TERM signal in "runsvctrl down"?
Date: Sat, 26 Jun 2004 10:17:35 +0200 [thread overview]
Message-ID: <20040626081735.GA16250@speedy.schwinge.homeip.net> (raw)
In-Reply-To: <m3pt7n9d9v.fsf@asfast.com>
On Sat, Jun 26, 2004 at 12:03:02AM -0400, 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?
It'll do so if apache was running before.
If it was not running it will just be started.
> In this case, the cleanup stuff in the script will get
> re-invoked on restart, correct?
Yes.
Regards,
Thomas
next prev parent reply other threads:[~2004-06-26 8:17 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 [this message]
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=20040626081735.GA16250@speedy.schwinge.homeip.net \
--to=schwinge-lists-skarnet.org-supervision@nic-nac-project.de \
--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).