From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1119 Path: news.gmane.org!not-for-mail From: Charlie Brady Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Runit on sl3 Date: Fri, 26 May 2006 16:18:11 -0400 (EDT) Message-ID: References: <7231C15EAC2F164CA6DC326D97493C8B01C1DE38@exchange35.fed.cclrc.ac.uk> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: sea.gmane.org 1148674709 7027 80.91.229.2 (26 May 2006 20:18:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 26 May 2006 20:18:29 +0000 (UTC) Cc: supervision@list.skarnet.org Original-X-From: supervision-return-1355-gcsg-supervision=m.gmane.org@list.skarnet.org Fri May 26 22:18:26 2006 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1FjilC-00029d-Ur for gcsg-supervision@gmane.org; Fri, 26 May 2006 22:18:15 +0200 Original-Received: (qmail 14430 invoked by uid 76); 26 May 2006 20:18:35 -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 14421 invoked from network); 26 May 2006 20:18:35 -0000 X-X-Sender: charlieb@e-smith.charlieb.ott.istop.com Original-To: "Nandakumar, R (Raja)" In-Reply-To: <7231C15EAC2F164CA6DC326D97493C8B01C1DE38@exchange35.fed.cclrc.ac.uk> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1119 Archived-At: On Fri, 26 May 2006, Nandakumar, R (Raja) wrote: > I would like to know if there have been any known problems while using > the runit class of commands on scientific linux. Two of the problems we > see are : > > 1. runsv does not automatically fork and make itself a background job. Why do you see that as a problem? runsv should only be run by runsvdir, which will then wait for it to complete. > 2. runsv and runsvdir occasionally die Do you know why they do? My guess is that you have had severe memory overcommitment, and they are being killed by the "Out of Memory" killer of the linux kernel. They won't have been the only processes killed (but perhaps they would be the most noticable ones*). But if there's any other cause of them dying, then I'm sure Gerrit would be interested to know. --- Charlie * runsv will be replaced automatically, but service will be in down state if there is a "down" file, whereas it might have been running when the runsv died/was killed. Hence, death of runsv might be quite noticeable.