ping handles float intervals incorrectly

[dovsienko]

This uses an interval of one second (correct):

~> ping -n -i 1 127.0.0.1
~> ping -n 127.0.0.1

This uses an interval of two seconds (correct):

~> ping -n -i 2 127.0.0.1

This rejects an invalid interval value (correct):

~> ping -n -i 0 127.0.0.1
error: bad timing interval: 0
~> ping -n -i -1 127.0.0.1
error: bad timing interval: -1

This uses an interval of one second (incorrect):

~> ping -n -i 1.99999999 127.0.0.1

This receives the first reply and then waits indefinitely until Ctrl-C:

~> ping -n -i 0.99999999 127.0.0.1

If this implementation of ping does not support float intervals, it should reject such values with an error message, as it does above.

[dovsienko]

The practical meaning of this is, I often run ping with "-i 0.2" to have a faster feedback loop when troubleshooting network issues. When the output stops after the first reply, on the surface it looks the same as a network problem.

[waddlesplash]

Fixed by merging a newer FreeBSD ping in hrev57594.