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.
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe"
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the
Trouble? Email listmas...@chrony.tuxfamily.org.