6e24d33517
Currently, we run sv start immediately after linking the service. The runsv process may not be up at the moment, as a result of which openrc will mark the service as stopped, even though it may be brought up by runit at the next scan. This is documented in the gentoo wiki: https://wiki.gentoo.org/wiki/Runit#OpenRC.27s_runit_integration_feature This PR adds a timeout so that correct process state can be reported. Before: * Starting netdata-runit ... fail: /run/openrc/sv/netdata: runsv not running * Failed to start netdata-runit After: * Starting netdata-runit ... fail: /run/openrc/sv/netdata: runsv not running ok: run: /run/openrc/sv/netdata: (pid 9042) 0s This fixes #253. |
||
---|---|---|
.. | ||
.gitignore | ||
binfmt.sh.in | ||
cgroup-release-agent.sh.in | ||
functions.sh.in | ||
gendepends.sh.in | ||
init-early.sh.Linux.in | ||
init.sh.BSD.in | ||
init.sh.GNU-kFreeBSD.in | ||
init.sh.GNU.in | ||
init.sh.Linux.in | ||
Makefile | ||
meson.build | ||
openrc-run.sh.in | ||
rc-cgroup.sh | ||
rc-functions.sh | ||
rc-mount.sh | ||
runit.sh | ||
s6.sh | ||
start-stop-daemon.sh | ||
supervise-daemon.sh |