On Thu, Jan 30, 2014 at 03:03, Nathanael Rensen wrote: > I noticed that ntpd(8) was regularly reporting it was unsynced, which > in turn impacts down stream clients. > > ntpd_adjtime() in usr.sbin/ntpd/ntpd.c uses the olddelta returned by > adjtime(2) to determine whether the previous adjustment was completed. > The clock is considered to be synced only if olddelta is zero. However, > olddelta may be returned using a non-normalised zero, which is not the > zero that ntpd_adjtime() is expecting. ntpd(8) will then report that it > is unsynced, even though the previous adjustment was completed.
Yup. We noticed that too. A fix should be committed shortly. Thanks.
