From: Gerrit Pape <pape@smarden.org>
Subject: Re: runit write access
Date: Thu, 20 Jul 2006 09:57:09 +0000 [thread overview]
Message-ID: <20060720095709.1497.qmail@1fe30da389e686.315fe32.mid.smarden.org> (raw)
In-Reply-To: <1153223749.15280.0.camel@localhost>
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.
prev parent reply other threads:[~2006-07-20 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 11:55 Pascal de Bruijn
2006-07-20 9:57 ` Gerrit Pape [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060720095709.1497.qmail@1fe30da389e686.315fe32.mid.smarden.org \
--to=pape@smarden.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).