Re: supervised processes controlled by non-root user?

[Robin Bowes <robin-lists@robinbowes.com>]

Gerrit Pape wrote:
> On Thu, Sep 15, 2005 at 09:30:02AM +0100, 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)
> 
> 
> Add (e.g.)
> 
>  chown <user> ./supervise ./supervise/ok ./supervise/control ./supervise/status
> 
> to the top of the ./run script.  Now <user> can use svc to control the
> service, and svstat query status informations.

Does it need to go in the run script? Or will a one-off "chown -R
./supervise user" do the trick? Tell you what, I'll try it :)

Answer: the one-off command seems to work. ./supervise/status gets
chowned root but has 644 perms so is world-readable. In fact, chown user
./supervise/status in the run file doesn't set the owner of status anyway.

In summary, I did the following:

chown -R uname:group /service/svcname/supervise \
   /service/svcname/log/supervise

The user "uname" can now control the service svcname.

Presumably this would work even if the service in question uses
privileged ports as the actual starting and stoping of the service is
done by the svscan process which is started by svscanboot?

> Or, if the complete service should be owned by the user, see
>  http://article.gmane.org/gmane.comp.sysutils.supervision.general/795

This is a "nicer" solution. Is this possible with daemontools, or only
using your runit package?

Thanks v. much.

R.
-- 
http://robinbowes.com

If a man speaks in a forest,
and his wife's not there,
is he still wrong?