Hi Miroslov
There is a new release of macOS 10.13 out today but as yet no fix for the
adjtime() issue.
> On 11/07/2017, at 2:49 AM, Miroslav Lichvar wrote:
>
> Is it really 5000 ppm on macOS 10.13? There is a testing program
> test/kernel/adjtime, which should print the maximum slew rate. You
>
> On 11/07/2017, at 2:49 AM, Miroslav Lichvar wrote:
>
> On Mon, Jul 10, 2017 at 08:03:19PM +1200, Bryan Christianson wrote:
>>
>> +With the exception of macOS 10.12 and earlier, all systems have operating
>> system
>
> Would it better to say "all supported systems" ?
OK - I'll change that.
On Mon, Jul 10, 2017 at 08:03:19PM +1200, Bryan Christianson wrote:
> macOS 10.13 will implement the ntp_adjtime() system call, allowing better
> control over the system clock than is possible with the existing adjtime()
> system call.
> chronyd will support both the older and newer calls, enabling
On Sat, Jul 01, 2017 at 11:54:07AM +1200, Bryan Christianson wrote:
> Not sure if this is related to the current commits or if its an earlier
> issue.
> I had to exclude macOS from MOD_TAI because txc does NOT have a field called
> tai.
It is a bug. It seems only on Linux the timex struct has t
macOS 10.13 will implement the ntp_adjtime() system call, allowing better
control over the system clock than is possible with the existing adjtime()
system call.
chronyd will support both the older and newer calls, enabling binary code to
run without recompilation on macOS 10.9 through macOS 10.13
