From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1207 Path: news.gmane.org!not-for-mail From: Gerrit Pape Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runit write access Date: Thu, 20 Jul 2006 09:57:09 +0000 Message-ID: <20060720095709.1497.qmail@1fe30da389e686.315fe32.mid.smarden.org> References: <1153223749.15280.0.camel@localhost> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1153389415 10451 80.91.229.2 (20 Jul 2006 09:56:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 20 Jul 2006 09:56:55 +0000 (UTC) Original-X-From: supervision-return-1443-gcsg-supervision=m.gmane.org@list.skarnet.org Thu Jul 20 11:56:53 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 1G3VH1-0002o7-P8 for gcsg-supervision@gmane.org; Thu, 20 Jul 2006 11:56:51 +0200 Original-Received: (qmail 8629 invoked by uid 76); 20 Jul 2006 09:57:12 -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 8624 invoked from network); 20 Jul 2006 09:57:12 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <1153223749.15280.0.camel@localhost> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1207 Archived-At: On Tue, Jul 18, 2006 at 01:55:49PM +0200, Pascal de Bruijn wrote: > I've run into some issue with runit, which I think are related to it not > having write access to the root fs. > > To which files does runit need write access? I think it's just the ./supervise/ subdirectories in the service and log service directories, and the magic files stopit and reboot in /etc/runit/, but I may miss some. And there's the ./down file that runit doesn't touch itself, but external programs my want to. All files runit needs write access to can be symbolic links pointing to a ramdisk for example. They can be dangling symlinks, runit should cope with this well, if not, I'd consider it a bug. HTH, Gerrit.