-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jan 29, 2006, at 8:32 AM, Adrian von Bidder wrote:
You're correct on both counts - BUT: accuracy to within a few tens
of ms is
solved, it's not a problem. Servers are thrown out of the pool
when they
reach something like 50ms offset (Ask - what value do you currently
use?)
100ms; although your score drops very slowly at that offset. For
example my DSL was overloaded last night, so the score on my ntp box
at home dropped a bit:
http://www.pool.ntp.org/scores/64.81.84.140
Again, the code for the pool is at
https://svn.develooper.com/projects/ntppool/trunk/
(the bit that checks the servers is in the "pool" script, around line
250).
Since you should always use 3 or more servers if time
synchronisation is
important to you the 'clock drifts out to 10 seconds' case just won't
happen in practice - unless you lose sync altogether, which is a
reliability problem.
Reliability, as in 'will the ntp server have the same IP over several
months' is imho the unsolved problem, especially in the pool where
many
servers are operated by hobbyists and small entities.
If the pool ever grows to a point where we have more than plenty
servers then we can add something to only (or mostly) use servers
after they have stayed stable for months.
First we need more servers though! :-)
- ask
- --
http://askask.com/ - http://develooper.com/
-----BEGIN PGP SIGNATURE-----
iQCVAwUBQ+MKpvkoKP1ixIspAQIllgP7BHyrw4rsGIREl1zAa6dsMbJHQE/T3Oyt
YHLUkbqm9OH3MJFFFBfZEg3SGzK01VN6c15BXu84LmlmkxJLt3IpD+955qrjWd2p
cNTgcpdAbh2LtF/p2jeJoY0paK0NsUCYkkU8SNelRauHywPyD2QKHDThHbjBgeVg
x72Ix4zDU24=
=lQ5s
-----END PGP SIGNATURE-----
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
