Re: Problem booting after Yum update of FC4
- From: Mike McCarty <mike.mccarty@xxxxxxxxxxxxx>
- Date: Thu, 08 Dec 2005 10:37:41 -0600
Tim wrote:
someone suggested:
Try "ping google.com" for several hours, and see how many packets you drop.
Tim:
I hope you don't mean continuously. That would constitute abuse.
James Wilkinson:
That's a fairly harsh definition of abuse you've got.
It fits mine. It's not an attack, but it is an abuse. Having a ping test for 30 sec or so probably wouldn't bother anyone, but running it "for several hours" would sure fit my definition of "abuse".
They've made the ping service available in the same way as they make the HTTP service available. Accessing Google's web pages once a second would not be OTT for a suitably busy site.
What makes you think that Google has provided you with a ping responder?
Exactly, right on the mark, correct.
[snip continuous pinging sometimes necessary]
Fair enough, but do such things with the consent of the equipment owners. If you're testing your equipment, do so against someone that doesn't mind it.
Yep. Or buy your own.
This guy sounds like "it doesn't matter that I broke into the car repair shop and used the tools there, because I put them all back when I was through with them."
I suggest this: do you have a router? Try pinging that. I use a router between my DSL modem and my machine. It responds to pings. So does my DSL modem, for that matter.
$ ping dslmodem PING dslmodem (192.168.0.1) 56(84) bytes of data. 64 bytes from dslmodem (192.168.0.1): icmp_seq=0 ttl=63 time=2.60 ms 64 bytes from dslmodem (192.168.0.1): icmp_seq=1 ttl=63 time=1.26 ms 64 bytes from dslmodem (192.168.0.1): icmp_seq=2 ttl=63 time=1.19 ms
--- dslmodem ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 1.194/1.689/2.606/0.649 ms, pipe 2
$ ping router PING router (172.17.100.199) 56(84) bytes of data. 64 bytes from router (172.17.100.199): icmp_seq=0 ttl=127 time=0.562 ms 64 bytes from router (172.17.100.199): icmp_seq=1 ttl=127 time=0.579 ms 64 bytes from router (172.17.100.199): icmp_seq=2 ttl=127 time=0.569 ms 64 bytes from router (172.17.100.199): icmp_seq=3 ttl=127 time=0.570 ms 64 bytes from router (172.17.100.199): icmp_seq=4 ttl=127 time=0.571 ms 64 bytes from router (172.17.100.199): icmp_seq=5 ttl=127 time=0.565 ms
--- router ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 4999ms rtt min/avg/max/mdev = 0.562/0.569/0.579/0.020 ms, pipe 2
[snip]
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
- Follow-Ups:
- Re: Problem booting after Yum update of FC4
- From: James Wilkinson
- RE: Problem booting after Yum update of FC4
- From: Tony Foster
- Re: Problem booting after Yum update of FC4
- References:
- Re: Compusa 54MB Wireless G PC Card for Fedora4
- From: David G. Miller (aka DaveAtFraud)
- Problem booting after Yum update of FC4
- From: Tony Foster
- Re: Problem booting after Yum update of FC4
- From: James Wilkinson
- Re: Problem booting after Yum update of FC4
- From: Tim
- Re: Problem booting after Yum update of FC4
- From: James Wilkinson
- Re: Problem booting after Yum update of FC4
- From: Tim
- Re: Compusa 54MB Wireless G PC Card for Fedora4
- Prev by Date: Re: Cups Troubles
- Next by Date: Realtime Replication of a Single File
- Previous by thread: Re: Problem booting after Yum update of FC4
- Next by thread: RE: Problem booting after Yum update of FC4
- Index(es):
Relevant Pages
|