From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Linux startup issue
Date: Sat, 14 Aug 2004 02:58:26 -0400 [thread overview]
Message-ID: <m3y8kigq8n.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <c1.01.2sP145$5AJ@J.de.Boyne.Pollard.localhost> (Jonathan de Boyne Pollard's message of "Fri, 13 Aug 2004 09:41:08 +0000")
Jonathan de Boyne Pollard <J.deBoynePollard@Tesco.NET> wrote:
> 2. "Restart" is better implemented as "svc -t" rather than as "svc
> -du", since the latter has the side-effect of changing the current
> state (to "up") whereas the former does not.
More specifically:
- If the service is down to begin with, "svc -t" will have no effect;
"svc -du" will bring the service up, with automatic restarting.
- If the service is running once from "svc -o", then "svc -t" will
take it down and leave it down; "svc -du" will take it down and
bring it back up, with automatic restarting; "svc -do" will take it
down and bring it back up, without automatic restarting, just as it
was originally. (supervise publishes enough information in
supervise/status to distinguish the "-o" state from the "-u" state,
but svstat doesn't report it.)
- "svc -d" sends SIGTERM and SIGCONT, so if the service is stopped
with SIGSTOP, it will be allowed to run again so it can exit.
"svc -t" sends only SIGTERM, which is not sufficient to kill a
stopped process, but it can be combined with "svc -c" for the same
effect as "svc -d" (without turning off restarting).
paul
next prev parent reply other threads:[~2004-08-14 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0408121801310.23255@avion.km3t.org>
2004-08-13 9:41 ` Jonathan de Boyne Pollard
2004-08-14 6:58 ` Paul Jarc [this message]
2004-08-14 17:20 ` Stefan Karrmann
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=m3y8kigq8n.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).