On Sep 8, 2005, at 9:21 AM, Brad Knowles wrote:
[...]
Moreover, the same servers are used in the parent zone as well as
in the numbered sub-zones, so there's a good chance that you'll get
a duplicate record.
No, the chance is the same. If there are enough servers to make the
zones non-duplicate, they will all be. (Otherwise there's an equal
chance of overlap between all of them).
I think Adrian told this before and I haven't changed that part of
the system. :-)
The OP was asking if it made sense to also include an explicit
3. sub-zone, at least in the zones where it makes sense, so that we
can make sure that there is no duplication between any of the
numbered sub-zones and that this will give us the minimum four
upstream time servers that are needed to be able to deal with a
single falseticker.
I have a few ideas related to this. I'll think about it some more.
The first thing I want to do is to have the /zone/ page on the
www.pool.ntp.org site have a "recommended server configuration" listed.
- ask
--
http://www.askbjoernhansen.com/
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
