Date: Mon, 24 Apr 2000 12:35:04 -0400 From: "Jason J. Horton" <jason@intercom.com> To: Rahul Siddharthan <rsidd@physics.iisc.ernet.in>, questions@freebsd.org Subject: Re: question about ping(8) Message-ID: <390477B8.4D340157@intercom.com> References: <39046FCE.143CAFC0@intercom.com> <20000424214137.A951@physics.iisc.ernet.in>
next in thread | previous in thread | raw e-mail | index | archive | help
Rahul Siddharthan wrote: > > > left a ping running all weekend, came back Monday to get this. > > > > 64 bytes from 10.10.10.2: icmp_seq=60393 ttl=255 time=0.544 ms > > ^C > > --- 10.10.10.2 ping statistics --- > > 322538 packets transmitted, 322538 packets received, 0% packet loss > > round-trip min/avg/max/stddev = 0.470/0.565/30.742/0.234 ms > > > > Any reason the ping stopped logging at 322538 packets? > > Maybe because you hit ^C? :-) > > 322538 packets at the default 1 packet per second works out to > 89.5 hours, or 3 days 17.5 hours. Seems consistent with your > "all weekend" if it was a long weekend. Maybe I am crazy, but does the icmp_seq "roll over" at some point? Why dont the two match. > Any reason why you did this? Odd behavior from a 3.4-STABLE box. The server will occasionally stop responding completely for a few minutes, and will bring itself back. The server didnt hang or reboot, uptime reports as it should. Am thinking it may be an improper setting in BIOS for APM or flakey fxp0 or HDD. Seems that a constantly pinging the server stops this odd behavior. -- -Jason J. Horton <jason@intercom.com> Fat Man in a Little Coat Intercom Online Inc. 212.376.7440 ext 21 | http://www.intercom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?390477B8.4D340157>