From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/698 Path: main.gmane.org!not-for-mail From: Lars Kellogg-Stedman Newsgroups: gmane.comp.sysutils.supervision.general Subject: Respawn limit for runsv? Date: Fri, 11 Feb 2005 07:56:46 -0500 Message-ID: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1108164679 11313 80.91.229.2 (11 Feb 2005 23:31:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 11 Feb 2005 23:31:19 +0000 (UTC) Original-X-From: supervision-return-937-gcsg-supervision=m.gmane.org@list.skarnet.org Sat Feb 12 00:31:19 2005 Original-Received: from antah.skarnet.org ([212.85.147.14] ident=qmailr) by ciao.gmane.org with smtp (Exim 4.43) id 1CzkFg-0003vo-CA for gcsg-supervision@gmane.org; Sat, 12 Feb 2005 00:31:08 +0100 Original-Received: (qmail 25169 invoked by uid 76); 11 Feb 2005 23:33:24 -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 25163 invoked from network); 11 Feb 2005 23:33:24 -0000 X-Injected-Via-Gmane: http://gmane.org/ Original-To: supervision@list.skarnet.org Original-Lines: 19 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 209-6-203-41.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com User-Agent: MT-NewsWatcher/3.4 (PPC Mac OS X) Original-Sender: news X-MailScanner-To: gcsg-supervision@gmane.org Xref: main.gmane.org gmane.comp.sysutils.supervision.general:698 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:698 Howdy, Has anyone investigated adding some sort of respawn limiter to runit? I figure that if a program is crashing immediately every time it runs, it probably doesn't need to be restarted -- which just floods the logs with error message, perhaps overwriting critical log data about what precipitated the problem in the first place. I'm thinking of some sort of setting that will down a service if it dies more than m times in n seconds. This would be controlled via a file in the service directory...maybe we can introduce a 'config' file, similar to what svlogd uses, to allow per-service configuration? Alternatively, this could perhaps be farmed out to a wrapper program, so that a run script might look like: exec respawn_wrapper ... Any thoughts?