From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/712 Path: main.gmane.org!not-for-mail From: Thomas Schwinge Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Respawn limit for runsv? Date: Sun, 13 Feb 2005 22:21:45 +0100 Message-ID: <20050213212145.GA1092@hera.lehmann.schwinge.homeip.net> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1108329731 19992 80.91.229.2 (13 Feb 2005 21:22:11 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 13 Feb 2005 21:22:11 +0000 (UTC) Cc: Lars Kellogg-Stedman , supervision@list.skarnet.org Original-X-From: supervision-return-951-gcsg-supervision=m.gmane.org@list.skarnet.org Sun Feb 13 22:22:11 2005 Original-Received: from antah.skarnet.org ([212.85.147.14] ident=qmailr) by ciao.gmane.org with smtp (Exim 4.43) id 1D0RBq-00022K-VP for gcsg-supervision@gmane.org; Sun, 13 Feb 2005 22:22:03 +0100 Original-Received: (qmail 9271 invoked by uid 76); 13 Feb 2005 21:24:27 -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 9265 invoked from network); 13 Feb 2005 21:24:26 -0000 Original-To: Charlie Brady Mail-Followup-To: Charlie Brady , Lars Kellogg-Stedman , supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-MailScanner-To: gcsg-supervision@gmane.org Xref: main.gmane.org gmane.comp.sysutils.supervision.general:712 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:712 On Sun, Feb 13, 2005 at 01:42:01PM -0500, Charlie Brady wrote: > On Sat, 12 Feb 2005, Lars Kellogg-Stedman wrote: > > - The disk fills up, causing your X startup to fail. But because of the > > continuous respawning, you can't log in on the console! This has happened to me, too. :-( (And of course no telnetd, sshd or similar was running...) > It would also be useful to have a mechanism to distinguish between a > process dying in reponse to a request from runsv, and a program dying > unexpectedly. Perhaps have "finish" and "unexpected_finish" scripts. I'd > certainly like to have a mechanism to run a finish script if a service is > taken down, but not if it just died unexpecedly. The "unexpected_finish" > script could introduce the programmed delay you want, notify the admin, > preserve any essential logs, etc. I'd suggest to only have 'finish', but have it passed a) the information how the process (was) terminated (i.e. either manually using svc, runsvctrl, writing to 'SERVICE/supervise/control' or because of the process's termination) and b) the process's exit-code. This information could be passed either using positional parapeters or via environment variables. Regards, Thomas