From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/554 Path: main.gmane.org!not-for-mail From: prj@po.cwru.edu (Paul Jarc) Newsgroups: gmane.comp.sysutils.supervision.general,gmane.network.djbdns Subject: Re: Linux startup issue Date: Sat, 14 Aug 2004 02:58:26 -0400 Organization: What did you have in mind? A short, blunt, human pyramid? Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1092466744 22954 80.91.224.253 (14 Aug 2004 06:59:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 14 Aug 2004 06:59:04 +0000 (UTC) Original-X-From: supervision-return-792-gcsg-supervision=m.gmane.org@list.skarnet.org Sat Aug 14 08:58:57 2004 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14]) by deer.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 1BvsVF-0006jX-00 for ; Sat, 14 Aug 2004 08:58:57 +0200 Original-Received: (qmail 1001 invoked by uid 76); 14 Aug 2004 06:59:18 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 996 invoked from network); 14 Aug 2004 06:59:18 -0000 X-pymsgauth-token: 87a7eac37bd8243e5f56d8ef90f093679877a40d Original-To: dns@list.cr.yp.to, supervision@list.skarnet.org In-Reply-To: (Jonathan de Boyne Pollard's message of "Fri, 13 Aug 2004 09:41:08 +0000") Mail-Copies-To: nobody Mail-Followup-To: dns@list.cr.yp.to, supervision@list.skarnet.org Original-Lines: 23 User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) Xref: main.gmane.org gmane.comp.sysutils.supervision.general:554 gmane.network.djbdns:10530 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:554 Jonathan de Boyne Pollard 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