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 ch
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 an
> On 8/08/2017, at 6:25 PM, Miroslav Lichvar wrote:
>
> 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),
On Tue, Aug 08, 2017 at 06:37:00PM +1200, Bryan Christianson wrote:
> One thing I did notice. On macOS 10.12 the frequency on the machine I use
> seems to mostly hover in the range 16 to 19 ppm, depending on temperature,
> other workload etc.
>
> On macOS 10.13, it seems to be more like 17.5 to