[ntp:questions] ntpd 4.2.4p5 pool pool.ntp.org preempt

David Mills mills at udel.edu
Sat Apr 25 02:41:47 UTC 2009


BlackLists,

You should read the 
http://www.eecis.udel.edu/~mills/ntp/html/manyopt.html page, especially 
where it talks about shedding excess
associations. This is the same clustering algorithm used with regular 
servers, except that the excess associations
are demobilized to minimuze excess network traffic. If you want more 
than the default minimum three, use the
minclock option of the tos command.

Dave

E-Mail Sent to this address will be added to the BlackLists wrote:

>A few Q, re:ntpd 4.2.4p5 pool pool.ntp.org preempt
>
>I asking the following, due to my observations, that with ntpd conf e.g.
>  server 0.vendor.pool.ntp.org preempt
>  server 1.vendor.pool.ntp.org preempt
>  server 2.vendor.pool.ntp.org preempt
>  server 3.vendor.pool.ntp.org preempt
>
> seems to (sometimes?) result in poor selection of time servers
>  only 4 IPs get used from the 4 pool host names,
>  the IPs never seem to change
>  (often) says 3 out the 4 servers are not suitable for synchronization
>    (not near-by NTP servers?)
>
>
>It appears that the ntp.conf, pool command isn't yet implemented?
> e.g. pool 1.north-america.pool.ntp.org
>
> e.g. server 1.north-america.pool.ntp.org
>  appears to result in grabbing only one of the DNS A returned IPs
>
>
> What should be the results of using the preempt flag?
>
>  It doesn't seem that the preempt flag does anything noticeable?
>   e.g. server 2.north-america.pool.ntp.org preempt
>
>   Using the Meinberg 1.03a NTP time server monitor,
>    the servers in the NTP status don't seem to change.
>
>
> Does the 3.vendor.pool.ntp.org try to dish out geographically(?)
>  close NTP servers?
>
>
>  
>




More information about the questions mailing list