-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi again,
Seems there are still some good guys out there, here is the reply i got from the abusive client ... > > I've noted some interesting behaviour that you may want to look in to. > One of the machines that was responsible for hammering your server was > running Gentoo. The operator of this machines had enabled ntpd, both > client and server. Stopping the server portion effectively stopped the > over-zealous ntp traffic. What I don't understand is why the ntp daemon > felt the need to hammer your servers (one machine at a rate of about 4 > requests/second). Both machines were using the stock /etc/ntpd.conf as > far as I could tell, so you may want to bring this up in a Gentoo forum > somewhere. > Now, I am not entirely up to scratch with the default behavior of NTP, so could someone help explain this behavior? Could it be a firewall blocking the replies as you mentioned and that would cause the server to try again? Johan Ask Bjørn Hansen wrote: > > On Apr 25, 2006, at 1:57 AM, Johan Lindquist wrote: > >>> True, but if it is simply a firewall issue, then this should probably >>> make it into the usage document perhaps? > > I'd guess that the people who aren't noticing their time not being set > wouldn't notice the note on our site either. > > > - ask > > -- > http://askask.com/ - http://develooper.com/ > > - -- you too? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEUHcR1Tv8wj7aQ34RAsCPAJsGKntgXYvbB7kmDSLoW1/JkgCbpACcCdG/ eWh58CtUjtb2rcxxgbCEr1c= =2kDx -----END PGP SIGNATURE----- _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
