Re: Getting a process to run as root

[Wayne Marshall <wcm@b0llix.net>]

On Fri, 27 Apr 2012 10:18:52 +0100
Peter Hickman <peterhickman386@googlemail.com> wrote:
 
> Here is the /etc/sv/runsvdir-log_watcher/run file
> 
> #!/bin/sh
> 
> RUNIT_USER=log_watcher:root:adm
> 
> exec 2>&1
> exec chpst -u$RUNIT_USER runsvdir /home/log_watcher/service
> 
> I've tried a variety of combinations and values for the -u and
> -U settings to no avail
> 
> The program runs but when it attempts to access the log files
> it no longer has permission to do so (just like it was before
> I added the missing groups to the log_watcher user).
> 

I see evidence of more than a few problems here.  For example,
why would you be using runsvdir in a service definition?

Anyway, it would appear that your basic runit installation and
setup may be a little confused.  Hopefully some runit users here
will be able to give you some good suggestions.

BTW, if you should ever decide to give perp a try, you may be
pleased to find you don't have to mess around with any symlink
indirection to install your service.  Then I could suggest an
rc.main runscript for your "log_watcher" service that looks
something like this:

#!/bin/sh
# /etc/perp/log_watcher/rc.main

exec 2>&1

TARGET=${1}
SVNAME=${2}

RUNUID="log_watcher"
GROUPS="log_watcher:adm"

start() {
  echo "starting ${SVNAME}..."
  exec runuid -S ${GROUPS} ${RUNUID} /path/to/log_watcher
}

reset() {
  echo "resetting ${SVNAME}..."
  exit 0
}

eval ${TARGET} "$@"

### EOF

Wayne
http://b0llix.net/perp/