Sergey Poznyakoff wrote:
Andy Furniss <[EMAIL PROTECTED]> wrote:
Thanks.
It fixes it for -i >=1 but -i <1 still gives invalid interval.
Interval should be an unsigned integer number. 0 interval is
is not allowed.
I want <1 not 0 but unsigned int would explain it, I asked if anyone
else had a ping that did -i <1 >0 and it seems there is one out there -
distro specific I suppose. From a mail I just received -
# ping -i 0.5 127.0.0.1 -c 10
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.065 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.054 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.065 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.063 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.066 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.063 ms
64 bytes from 127.0.0.1: icmp_seq=6 ttl=64 time=0.057 ms
64 bytes from 127.0.0.1: icmp_seq=7 ttl=64 time=0.053 ms
64 bytes from 127.0.0.1: icmp_seq=8 ttl=64 time=0.064 ms
64 bytes from 127.0.0.1: icmp_seq=9 ttl=64 time=0.062 ms
--- 127.0.0.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 4553ms
rtt min/avg/max/mdev = 0.053/0.061/0.066/0.006 ms, pipe 2
# tethereal icmp[0] == 8 and ip proto 1 -i lo
Capturing on lo
0.000000 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
0.510342 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
1.010297 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
1.521217 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
2.021163 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
2.532090 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
3.032023 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
3.542945 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
4.053885 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
4.553827 127.0.0.1 -> 127.0.0.1 ICMP Echo (ping) request
It generates packets every 0.5 sec.
Andy.
_______________________________________________
Bug-inetutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-inetutils
