From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/710 Path: main.gmane.org!not-for-mail From: Lars Kellogg-Stedman Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Respawn limit for runsv? Date: Sun, 13 Feb 2005 18:19:37 +0000 (UTC) Message-ID: References: <20050213134736.14448.qmail@d8e68f84add864.315fe32.mid.smarden.org> Reply-To: lars@oddbit.com NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1108319517 25332 80.91.229.2 (13 Feb 2005 18:31:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 13 Feb 2005 18:31:57 +0000 (UTC) Original-X-From: supervision-return-949-gcsg-supervision=m.gmane.org@list.skarnet.org Sun Feb 13 19:31:56 2005 Original-Received: from antah.skarnet.org ([212.85.147.14] ident=qmailr) by ciao.gmane.org with smtp (Exim 4.43) id 1D0OW5-0008BZ-Sj for gcsg-supervision@gmane.org; Sun, 13 Feb 2005 19:30:45 +0100 Original-Received: (qmail 7400 invoked by uid 76); 13 Feb 2005 18:33:19 -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 7394 invoked from network); 13 Feb 2005 18:33:19 -0000 X-Injected-Via-Gmane: http://gmane.org/ Original-To: supervision@list.skarnet.org Original-Lines: 21 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: slrn/0.9.8.1 (Linux) Original-Sender: news X-MailScanner-To: gcsg-supervision@gmane.org Xref: main.gmane.org gmane.comp.sysutils.supervision.general:710 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:710 > I also think a separate program is appropriate for such special > services. I'm not sure this should really be thought of as a special service; since the supervisor is responsible for restarting the target program, this would also seem to be the logical place to handle respawn limits. Having said that, an external implementation does work, although the code is a little more complicated since it becomes necessary to maintain some sort of external state. If the limiter were implemented in runsv, for example, it could all be managed internally without the necessity of reading and writing an external file. But with a working external solution, I'm probably too lazy to pursue anything else. -- Lars -- Lars Kellogg-Stedman