From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/626 Path: main.gmane.org!not-for-mail From: Lloyd Zusman Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Never mind ... Date: Sun, 07 Nov 2004 15:59:43 -0500 Message-ID: References: <20041107135411.13387.qmail@e25d0edd6a570d.315fe32.mid.smarden.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1099861320 15377 80.91.229.6 (7 Nov 2004 21:02:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 7 Nov 2004 21:02:00 +0000 (UTC) Original-X-From: supervision-return-865-gcsg-supervision=m.gmane.org@list.skarnet.org Sun Nov 07 22:01:47 2004 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14] ident=qmailr) by deer.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 1CQuAV-0007fi-00 for ; Sun, 07 Nov 2004 22:01:47 +0100 Original-Received: (qmail 28221 invoked by uid 76); 7 Nov 2004 21:02:07 -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 28215 invoked from network); 7 Nov 2004 21:02:07 -0000 X-Injected-Via-Gmane: http://gmane.org/ Original-To: supervision@list.skarnet.org Original-Lines: 23 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: hippo.asfast.net User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux) Cancel-Lock: sha1:75jATfY+kdprjjeVvPbUxM0aeAA= Original-Sender: news Xref: main.gmane.org gmane.comp.sysutils.supervision.general:626 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:626 Gerrit Pape writes: > Hm, if runsv has trouble starting the run script, it should pause for a > second before retrying, and not take up a high percentage of cpu. Can > you say what exactly was the permissions problem? > > Thanks, Gerrit. Well, all I noticed when I started poking around in the directory is that I got 'access denied' errors on some of the files there. At that point, I deleted the entire directory and recreated it, and then everything worked. I assume that this has to do with ownership or file permissions. I'm sorry that I can't give you more info. Next time something like this happens, I'll do a better job of collecting data before changing anything. -- Lloyd Zusman ljz@asfast.com God bless you.