On 2008-04-22, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] log]# ntpq -p > remote refid st t when poll reach delay offset jitter >======================================================================= > xdcf77 LOCAL(0) 11 u 130 1024 377 5.676 1307.74 320.974 > x193.204.114.232 .UTCI. 1 u 137 1024 377 20.074 511.544 152.824 > *LOCAL(0) LOCAL(0) 10 l 44 64 377 0.000 0.000 0.008
The Undisciplined Local Clock (LOCAL) is just a hack which allows ntpd to claim to be synchronized something when no real time sources are available. An ntpd claiming to be "synchronized" to LOCAL is actually just free-wheeling. You don't need, or want, to use LOCAL unless this ntpd is serving time to others. If you _really_ need to use LOCAL you should fudge it to stratum that is greater than all of your real time sources. In this case I'd use stratum 12. This ntpd only has two real time sources; it needs at least one more. When you have only two clocks you have no way of determining which is correct. When you have three, or more clocks, you can use the majority which agree (which is, in fact, exactly what ntpd does). -- Steve Kostecke <[EMAIL PROTECTED]> NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
