From: tkooda-list-skarnet.org-supervision-dated-60128960.bmlhi@devsec.org
Subject: Re: supervised processes controlled by non-root user?
Date: Wed, 26 Oct 2005 05:12:30 -0500 [thread overview]
Message-ID: <20051026101230.GG25536@rock.devsec.org> (raw)
In-Reply-To: <4329310A.8060002@robinbowes.com>
On Thu, 15 Sep 2005, Robin Bowes wrote:
> Is it possible to set up services that can be controlled by non-root
> users? If so, how?
>
> (using daemontools 0.76)
I supervise another copy of svscan for each user so they can
add/delete/control their own services:
http://devsec.org/info/superviseuser.html
(the same could be done using runit instead of daemontools)
--
Thor Kooda
next prev parent reply other threads:[~2005-10-26 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 8:30 Robin Bowes
2005-09-15 9:42 ` Gerrit Pape
2005-09-15 11:44 ` Robin Bowes
2005-09-15 12:05 ` Thomas Schwinge
2005-09-15 12:17 ` Robin Bowes
2005-10-26 10:12 ` tkooda-list-skarnet.org-supervision-dated-60128960.bmlhi [this message]
2005-10-30 12:43 ` Robin Bowes
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=20051026101230.GG25536@rock.devsec.org \
--to=tkooda-list-skarnet.org-supervision-dated-60128960.bmlhi@devsec.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).