From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1908 Path: news.gmane.org!not-for-mail From: Charlie Brady Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: endless loop at stage 2 of runit of run scripts of each service directories. Date: Mon, 11 Aug 2008 10:13:37 -0400 (EDT) Message-ID: References: <489FDBFF.4020206@elitecore.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: ger.gmane.org 1218464135 20692 80.91.229.12 (11 Aug 2008 14:15:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 11 Aug 2008 14:15:35 +0000 (UTC) Cc: supervision@list.skarnet.org To: Amrish Purohit Original-X-From: supervision-return-2143-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Aug 11 16:16:27 2008 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by lo.gmane.org with smtp (Exim 4.50) id 1KSYAS-0001Y7-B3 for gcsg-supervision@gmane.org; Mon, 11 Aug 2008 16:14:40 +0200 Original-Received: (qmail 2815 invoked by uid 76); 11 Aug 2008 14:14:02 -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 2800 invoked from network); 11 Aug 2008 14:14:02 -0000 X-X-Sender: charlieb@e-smith.charlieb.ott.istop.com In-Reply-To: <489FDBFF.4020206@elitecore.com> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1908 Archived-At: On Mon, 11 Aug 2008, Amrish Purohit wrote: > here is the format of run script > --------------------------------------- > #!/bin/bash > exec /etc/rc.d/init.d/cpuspeed start Doing that will always get you into trouble. init.d scripts are always designed to terminate quickly. That's exactly the opposite of what you want. Any program which you exec from a supervise run script is expected to keep running until you send it a signal asking for it to stop. You will need to look through /etc/rc.d/init.d/cpuspeed and find out what commands it calls, and find a way to call the same command in a way where the command will not terminate (e.g. don't run it in the background, or run it with an argument which tells it to run in the foreground). [Try: exec /usr/sbin/cpuspeed Or just use a symlink to /usr/sbin/cpuspeed as your /service/cpuspeed/run. ]