In article <[EMAIL PROTECTED]>, Richard B. Gilbert <[EMAIL PROTECTED]> wrote:
> Look at your /etc/ntp.conf. In that file, look at the server > statements. Do they include the keyword MINPOLL? Or MAXPOLL? He included it in his original posting and it has been (over) quoted several times since. He had no minpoll or maxpoll. It's really not uncommon for the poll interval to stick at the maximum once the system has stabilised. If close tracking is important, he probably wants to make one machine be a client only and only of the other machine. Looking at the most recent RFC (RFC 1305, for version 3), it looks to me that what most people wanting to improve phase tracking do, namely *reducing* maxpoll, won't actually work, because the poll interval is controlled by the loop time constant, not the other way round. However, this is based on only a quick skim of the area around page 95 of the PDF version, so I may have missed a back coupling between poll interval and time constant. Assuming that version 4 works in a similar way, I can't find a tinker option in version 4.2.0 which would seem to me to control this, although tinker allan is probably in the right area, but I'm not sure what it exactly does and I think it may affect the most responsive limit, rather than the least responsive one. Basically, though, NTP aims to give a best estimate of true time, not to give close tracking of machines that don't have access to very high quality measurements of true time. _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
