From: Joan Picanyol i Puig <lists-supervision@biaix.org>
To: supervision@list.skarnet.org
Subject: Re: installing runit as a user...
Date: Fri, 22 Oct 2010 02:20:18 +0200 [thread overview]
Message-ID: <20101022002018.GA18339@grummit.biaix.org> (raw)
In-Reply-To: <20101021234625.GE5055@bonnie.galis.org>
* George Georgalis <george@galis.org> [20101022 01:43]:
> On Thu 21 Oct 2010 at 06:27:09 PM -0400, Jameson Rollins wrote:
> >On Thu, 21 Oct 2010 14:16:36 -0700, George Georgalis <george@galis.org> wrote:
> >> I'd like to use runit and svlogd as a user in a couple
> >> applications (eg x11 sessions and desktop widgets) and I was
> >> wondering what experiences people have had with this?
> >
[...]
> >I have also been experimenting with "user runsvdir" instances that are
> >controlled by the system runsvdir instance. If the user has a ~/.sv
> >directory, the user runsvdir process manages run dirs in that directory.
[...]
>
> great idea, I don't imagine you have sv configured to look in
> ~/sv or some such?
>
> managing the path to sv and the path sv uses could get confusing
> since I normally use the sgid on the supervise directory to
> control root services as a user...
The only managing headache that I've found is permissions in
directories. You want to allow users read only access to their
supervisors' logs, not more. I have a vague recollection of this being
discussed previously.
qvb
--
pica
next prev parent reply other threads:[~2010-10-22 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 21:16 George Georgalis
2010-10-21 22:27 ` Jameson Rollins
2010-10-21 23:46 ` George Georgalis
2010-10-22 0:20 ` Joan Picanyol i Puig [this message]
2010-10-22 22:07 ` Jameson Rollins
2010-10-21 22:39 ` Charlie Brady
2010-10-21 23:30 ` George Georgalis
2010-10-22 22:10 ` Jameson Rollins
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=20101022002018.GA18339@grummit.biaix.org \
--to=lists-supervision@biaix.org \
--cc=supervision@list.skarnet.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).