Re: Runit questions

From: Colin Booth <cathexis_at_gmail.com>
Date: Tue, 11 Oct 2016 15:42:44 -0700

On Oct 11, 2016 3:09 PM, "Andy Mender" <andymenderunix_at_gmail.com> wrote:
>
> Hello again,
>
> I'm rewriting some of the standard sysvinit and openrc scripts to ./run
> scripts
> and I have some problems with dbus. I took the ./run script from Void
Linux
> as the original runit documentation doesn't have an exemplary dbus script.
> Whenever I check the status of dbus via "sv status dbus", I get the
> following
> error: "warning: dbus: unable to open supervise/ok: file does not exist".
I know this sounds cheesy, but try giving the full path to your dbus
supervision directory (if the scan dir is /etc/service, pass
/etc/service/dbus). Runit has a compiled in default service dir, but if
runsvdir is pointing somewhere else then sv won't find it without some
help. Last I checked, the upstream default is /service, and the Debian
default is /etc/service.

> This
> makes no sense, as both /etc/sv/dbus/supervise/ and
> /var/service/dbus/supervise/
> contain the "ok" file. Below the run script from Void Linux:
> #!/bin/sh
> [ ! -d /run/dbus ] && install -m755 -g 22 -o 22 -d /run/dbus
> exec dbus-daemon --system --nofork --nopidfile
>
> Not sure what's wrong and why this run script needs to contain so many
> operands.
dbus doesn't provide a service managed option so you need the --no* set to
have it do the right thing. --nofork keeps it from backgrounding,
--nopidfile keeps it from dropping a pid, and --system loads the system
defaults.

Cheers!
-Colin
Received on Tue Oct 11 2016 - 22:42:44 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:19 UTC