-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
warning: timeout (-t) value larger than period (-p) produces unexpected results #142
Comments
fping 4.1 |
By looking at the documentation, I found that after fping 4.X, -t represents a separate timeout for each packet, so that the settings for -t and -p are not relevant, so whether this warning can be ignored ? |
I agree that the warning is a bit confusing and probably not needed. I have removed it. |
I am just confusing the heck out of myself here. the docs also say "In loop/count mode, the default timeout is automatically adjusted to match the "period" value (but not more than 2000ms). You can still adjust the timeout value with this option, if you wish to, but note that setting a value larger than "period" produces inconsistent results, because the timeout value can be respected only for the last ping." But it looks like the timeout I specify below is being respected for all pings? 20ms period, 70ms timeout:
20ms period, 100ms timeout:
|
warning: timeout (-t) value larger than period (-p) produces unexpected results
fping -r 0 -c 10 -B 1.0 -t 300 -i 0 -p 1 -u host1 host2 ... host1000
Hello, I want to consult, what will happen to the above warning? unexpected results ?
thanks!
The text was updated successfully, but these errors were encountered: