Nottorf, Stefan wrote: > remote refid st t when poll reach delay offset jitter > ======================================================================== > ====== > *10.x.y.z .PPS. 1 u 338 1024 377 0.454 -1.559 0.078 > name1.name 10.x.y.z 2 u 471 1024 376 0.209 1.763 0.093 > name2.name 10.x.y.z 2 u 1461 1024 374 0.001 2.652 0.206 > name3.name 10.x.y.z 2 u 596 1024 376 0.385 0.052 0.322 > LOCAL(0) .LOCL. 5 l 59 64 377 0.000 0.000 0.001 > > In short: does the column st refer to the stratum of the remote host OR > does it mean "If I synchronize to that remote host I will get to stratum
That of the remote host. Incidentally, why are you running the local clock driver at stratum 5? That should only be done if your machine is a server and is being synchronised to a reliable time source by means other than NTP. Local clock has no place at all on clients and should only be used on servers as a deliberate choice. When synchrnonised to an unreliable source, like the undisciplined local clock (including that clock as a fall back to external servers), it should be set to the highest stratum that is still acceptable to its clients, if used at all. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
