Hi. If you don't run runit as an init replacement you need to start runsvdir manually. There is currently no init script provided so I made one from the init script for svscan. Please put in portage. Best regards Frank Benkstein.
Created attachment 66738 [details] /etc/init.d/runsvdir init.d script
Can you, please, add this to portage? Thanks...
problems: - depend() has way too much crap - start() too complicated, whats with duplicate pid handling - stop() needs to call ssd --oknodo ... do you need to hide errors from runsvctrl ?
Created attachment 79808 [details] updated /etc/init.d/runsvdir This is the cleaner version, someone please make the former file obsolete and consider including this one in portage. Tested and works...
One more machine running this fine. Please add to portage...
is the depend() really needed ?
Well, that depends on what services you wish to be managed by runit but I think the "after net" is a safe default (in contrary to "intrusive" "need net") and shouldn't mean any harm.
> Well, that depends on what services you wish to be managed by runit but I think > the "after net" is a safe default (in contrary to "intrusive" "need net") and > shouldn't mean any harm. then you actually mean to say "use net" ?
Ah, you're right maybe. I've never been a depend() expert... :-(
ok, well only other thing i see is stop() doesnt return status properly if ssd failed but runsvctrl worked ...
Unfortunately I don't know much about start-stop-daemon and in fact I never really liked it anyway (that's why I use runit) so please do anything necessary to correct it.
Can anyone with start-stop-daemon skills please take a look at this one? Thanks...
Created attachment 84991 [details] runsvdir
Thanks a lot, please be sure to take a look at bug 128918 and provide a different init-script for versions >= 1.4, thanks... (there is no runsvctrl anymore)
someone who actually uses this needs to post an updated init.d script
