🚀 go-pugleaf

Dave Fitch (davidf@syd.csa.com.au) wrote:
> carl@oversteer.library.uwa.edu.au (Carl Brewer) writes:
> >I'm not sure what TIS have done, but whatever it was has worked, it's a 
> >peak time (11am WST, that's 2pm ESST)
> >
> >----1.23.130.139.in-addr.arpa PING Statistics----
> >104 packets transmitted, 103 packets received, 0% packet loss
> 
> Ahhh, this is possibly (?) a dumb question, but...
> why is 104 packets transmitted and 103 packets received
> counted as 0% packet loss??  Wasn't 1 packet lost there?

The 0% is quite simply due to rounding, the correct answer is 0.96%, but
as most things round down by default...

zaphod:~$ bc
bc 1.02 (Mar 3, 92) Copyright (C) 1991, 1992 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
1/104
0

In truth, 1 packet probable wasnt lost, it just returned after Carl hit
ctrl-c - a good reason for putting a packet count on the command line when 
using ping if you want most accurate pings, although it doesnt make that
much difference with small ping times.

  Scott.