This thread reminds me... I did some tests a few months back, and found that, in most circumstances, NTP is extremely good at handling very distant connections with no problem. The results were probably skewed somewhat in that I ran them from my server, sitting on a data center backbone, and not from a home connection, but unfortunately I don't have access to a home Linux box at the moment. (I'd be curious to see how this holds up on something like a home cable modem.)
Offsets varied from +1ms (within the US) to -4ms (Africa). They were run from my server, which syncs to a handful of nearby stratum 1's. >From LayeredTech's data center (inside Savvis) in Texas: oxygen ~ # ntpdate -q south-america.pool.ntp.org server 200.192.232.8, stratum 2, offset 0.021524, delay 0.23042 server 146.83.183.179, stratum 2, offset -0.002081, delay 0.17311 server 201.84.224.130, stratum 3, offset 0.004254, delay 0.19417 26 Apr 00:33:31 ntpdate[5828]: adjust time server 146.83.183.179 offset -0.002081 sec oxygen ~ # ntpdate -q africa.pool.ntp.org server 41.223.43.5, stratum 2, offset 0.086558, delay 0.62405 server 196.43.1.14, stratum 3, offset 0.005741, delay 0.32759 server 196.25.1.9, stratum 2, offset -0.006428, delay 0.29601 server 196.43.1.9, stratum 2, offset -0.007126, delay 0.32123 server 196.25.1.1, stratum 2, offset -0.004245, delay 0.29314 26 Apr 00:31:07 ntpdate[4913]: adjust time server 196.25.1.1 offset -0.004245 sec oxygen ~ # ntpdate -q us.pool.ntp.org server 66.191.139.147, stratum 2, offset 0.001096, delay 0.07080 server 65.111.164.223, stratum 2, offset -0.003190, delay 0.07475 server 66.250.45.2, stratum 3, offset 0.013041, delay 0.07225 server 63.89.76.60, stratum 2, offset 0.005535, delay 0.07397 server 209.67.219.106, stratum 3, offset 0.003419, delay 0.02605 26 Apr 00:34:36 ntpdate[6216]: adjust time server 66.191.139.147 offset 0.001096 sec Icing on the cake, the biggest offset of them all: oxygen ~ # ntpdate -q time.nist.gov server 192.43.244.18, stratum 1, offset 0.004834, delay 0.04408 26 Apr 00:31:20 ntpdate[5012]: adjust time server 192.43.244.18 offset 0.004834 sec -- Matt On Thu, Jun 5, 2008 at 12:16 PM, mm_202 <[EMAIL PROTECTED]> wrote: > > Hey guys, > > This may of already been brought up, but I think that it would be nice > to be able to specify NTP servers by more specific zones. Something like: > > mo.us.pool.ntp.org > ca.us.pool.ntp.org > wa.us.pool.ntp.org > etc > > Or if by state if going 'too far' then at least by region (pt,mt,ct,et). > > IMHO, this would help not only users, but servers as well. > > -- mm_202. > _______________________________________________ > timekeepers mailing list > [email protected] > https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
