[OT] NTP servers - was Re: Kernel clock issue "Clocksource tsc unstable"

[NoOp]

On 02/27/2009 07:36 PM, Ray Parrish wrote:
> NoOp wrote:
>> @Hal: next time, instead of rebooting (you'll still have to go to the
>> data center most likely), you might try
>> sudo /etc/network/if-up.d/ntpdate
>> first. If that resyncs the machine properly without the reboot, then you
>> might want to look into running ntp on those machines if you aren't
>> already. And if you are running ntp, have a look at the ntp source. You
>> can elect to have multiple sources; I use 0.us.pool.ntp.org and have
>> 1.us.pool.ntp.org as the backup. Just a thought...
>>   
> Here are a few more time servers to try. 8-)
> 
> server tick.usask.ca
> server tock.usask.ca
> server clock.tricity.wsu.edu
> server gilbreth.ecn.purdue.edu
> server molecule.ecn.purdue.edu
> server ntp.ubuntu.com
> server europium.canonical.com
> 
> My system regularly connects to all of them. It's the way it was set up 
> on install, as I haven't changed the configuration files for ntpd.
> 
> Later, Ray Parrish
> 

Yes, but I think that you may not be aware of the reasoning behind the
pool.ntp.org servers:

http://www.ntp.org/
 http://www.pool.ntp.org/

which is ease the load on the big timeservers and spread the load over
many servers.

I also purposely remove the ntp.ubuntu.com/canonical servers; I' don't
mind providing some data, but sync'ing to them just seems a little big
brother/Microsoft'ish to me.