| Re: [chrony-dev] macOS 10.13 beta 5 - adjtime() is fixed. |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] macOS 10.13 beta 5 - adjtime() is fixed.
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 8 Aug 2017 08:25:51 +0200
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com E59C2883C2
On Tue, Aug 08, 2017 at 08:11:29AM +1200, Bryan Christianson wrote:
> New release of macOS 10.13 out this morning and adjtime() appears to be behaving correctly now. I think we should leave the workaround/tests in place until 10.13 is released because Apple might break it again between now and then :)
>
> I re-ran the ntpadjtime and adjtime tests in in chrony - no change to the previous results in maximum skew.
That's good news. Thanks for the update.
I assume chronyd is working correctly when using both adjtime() and
ntp_adjtime()? When starting with an initial offset over 1 second and
not allowed to make a step (makestep/initstepslew), the clock is
slewed as expected, with no oscillations, etc?
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.