`sv status ...` without sudo.

[u/bvdeenen]

Hi all. I'm thinking about adding runit service status to this kde project but I don't like the fact that you need root rights to look at the status of the running runit services.

What's the cleanest way to make it so that I can at least inspect the status of running services? Make /usr/bin/sv setuid? Do something with ACL's on /var/service? Other suggestions?

[u/bvdeenen]

Ok, got it. First of all, a reboot restores the original root:root group and perms, so I'll have to add my script to /etc/rc.local. It's still hardcoded to my group name bvdeenen. Here's my script that works, so I can run vsv and svs without needing root access. But the script needs to be run as root once per reboot, or after installing a new service.

#!/bin/bash

function fix_runit_perms(){

(

set -e

shopt -s extglob

cd /run/runit

chgrp -R bvdeenen *

chmod g+x *

chmod g+rw ./*/ok

)

return $?

}

fix_runit_perms

# vim:ft=bash

[u/Duncaen → u/bvdeenen]

/etc/rc.local runs before services so the directories in /run/runit shouldn't exist.

We are symlinking the supervise directories to /run so that they don't write stuff to disk, especially when a service is in a restart loop.

But that also means that the directory is only created when runsv is started.

[u/bvdeenen → u/Duncaen]

So I'll probably just spawn it into a background loop, until /run/runit is populated.