Robert Wachinger <[EMAIL PROTECTED]> writes: > 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?
"Hack the daemon" is the most likely solution (despite of "iburst" and "burst"). > > 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). What about not running the new board in the cluster first? Ulrich _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
