On Fri, Feb 17, 2017 at 11:12:37AM +0100, Richard Cochran wrote: > On Fri, Feb 17, 2017 at 10:03:35AM +0000, Urs Ritzmann wrote: > > But I was still concerned that we could get such a transient for any > > reason. Perhaps NTP was not yet ready to tune the system clock which > > invalidates that initial measurement. > > But ntpd avoids sudden system clock adjustments, doesn't it?
Normally it does, but on start, if the offset is smaller than 128ms, it doesn't step the clock and depending on the time constant it may take hours to correct and stabilize. With the lastest ntpd version (4.2.8), it's faster. Running ntpdate before ntpd may help. -- Miroslav Lichvar ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
