[2019-09-13 15:18] Dmitry Bogatov <kact...@disroot.org> > > [ Lorenzo Puliti <lorenzo.r...@gmail.com> ] > > So there is still a lag of 1.5 seconds from the moment runsvdir > > detects a new directory and the moment the runsv process create the ok > > pipe. Also, i'm afraid this lag may be affected from the filesystem > > type and the hardware, so i need to keep a workaround like (1) in > > place. I'm waiting to test with a service that links the supervise > > directory into run (there is none currently), maybe it helps? Any > > hope to further reducing this lag? > > ... but 1.5 seconds to definitely too much. I hope to take a look and > make more accurate testing on this, but my AFK life got quite > distracting recently.
I found source of delay (sleep(1)) and reduced failure threhold in src/t/runtest.sh. Please find patches in wip2 branch (ca08d0a) and tell, whether they solve issue. Still there will be delay: ~11769034 nanoseconds (or 0.12 sec) on my computer on test suite, your mileage may vary depending on number of factors. So, probably you will need to watch to updates of /etc/service/.forced-rescan or wait till control pipe appears. -- Note, that I send and fetch email in batch, once in a few days. Please, mention in body of your reply when you add or remove recepients.
