Send first echo request at startup delay #25
Conversation
Send the first echo request at startup after specified delay (default 0ms). This is useful to receive initial status quicker when using longer send interval setting. Such as processes waiting on dpinger to start. But once started, don't need such frequent status.
NOYB
force-pushed
the
Send_At_Startup_Delay
branch
from
2e8ee3c
to
07798be
Compare
|
This change introduces a race condition in thread startup. If the desire is to send a probe as soon as possible, there are better ways to address this. I had such an approach in an early version of the code, but removed it as being not worth the effort given that most will be using 250ms probes. If you can explain your use case it would be helpful... What parameters are you starting dpinger with? Are you using long probe times? Thanks. |
|
The desire is to control when the first probe is sent, independently from the send interval. The use case was describe in the commit message. Quicker initial status when longer send interval is desired. So that for instance the starting of a process isn't unnecessarily delayed waiting for the longer send interval. Yes I am using longer probe times than the default (5 seconds, it suits my needs). But a 5 second initial probe delay does not. Could you please be so kind as to describe the race condition? If my solution doesn't meet your requirements could you please include such an option? Thanks. |
|
I see the use case for shortening or eliminating the initial delay. I don't see a use case for lengthening it. An early version of dpinger had code to eliminate the delay--I'll look at putting it back in. Thanks. |
|
This has been addressed. Thank you again @NOYB. |
Send the first echo request at startup after specified delay (default 0ms).
This is useful to receive initial status quicker when using longer send interval setting.
Such as processes waiting on dpinger to start. But once started, don't need such frequent status.