diff options
| author | Aaditya Bagga <aaditya_gnulinux@zoho.com> | 2018-11-06 20:26:33 +0530 |
|---|---|---|
| committer | William Hubbs <w.d.hubbs@gmail.com> | 2021-09-11 17:20:50 -0500 |
| commit | 6e24d335172b43286a284167c2d54d8f240fc9a0 (patch) | |
| tree | 94eb1b9468e0cafdf115f53a3f181356d82fd7c6 /FEATURE-REMOVAL-SCHEDULE.md | |
| parent | d65e603acd9b1f542069c59482c5e22502afa872 (diff) | |
[runit integration] give a bit of time to start the service
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.
Diffstat (limited to 'FEATURE-REMOVAL-SCHEDULE.md')
0 files changed, 0 insertions, 0 deletions