Robert Wachinger wrote: > Hi, > > did anybody else have the problem, to have to stabilize the frequency > discipline > faster than the normal 15 minutes to hours? Does any solution exist? > > We have here the requirement to have a replaced board (a fresh one from the > factory, > where a correct content of the drift file is unknown) up after 5 minutes in a > cluster, > which also means, that its time does not stray more than 10ms (within the > cluster). > > Any tips? > We tried here to "play" with minpoll, burst, initial drift files (value 0). > > > Regards, Robert >
Use "iburst" on all your server statements in ntp.conf. Be sure to use -q as an option when you start ntpd. This may not be enough but there is not much more you can do. A very good server or several very good servers may also help. The goodness of a server is strongly dependent on the quality of the network path between the server and your client. Is it possible to run this new board standalone before joining the cluster? If so, that could get you a valid drift file. _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
