| [chrony-users] chronyd broken on macOS Big Sur |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx, chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] chronyd broken on macOS Big Sur
- From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
- Date: Sat, 18 Jul 2020 10:05:06 +1200
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a1-4; h=Feedback-ID:X-Smtpcorp-Track:To:Date:Message-Id: Subject:From:Reply-To:Sender:List-Unsubscribe; bh=GZMJXalNhg4DzoGcUNykF1Rkeeyeumn1nfWOGoxdNn0=; b=G/2q4st7OYoT6UKWvUqpDD5i9U NfAXVgIG7WJIfQsdzsG3yQ3E5QLDi7Q/JWBtAh+0iMnvg2co47Ag4Pz8OW9zicVJHu9lHfErzALGF eD+Cv4J0W9XJPV/5AvGwy50LR57DYqRVgOhDGtz0G4sX1xRVKUXq7tOhy7hBzpDtPSvR/NZyazWvo U8+W+IRFoW460E423akJ4DOkQNa0ioPoGjZd21aqMXtOCtcT+8Ib8bv6iNcn5uZgeY6NT4AoGinkY 6xX8/78ZptsbspDSC/z+u4vhSvpH8ADExOD5nzoPL0yLUbnD57IAx7bJKlt/OOGybapk5Cc0K7pQh AkxB4T4w==;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=whatroute.net; i=@whatroute.net; q=dns/txt; s=s149811; t=1595023524; h=from : subject : to : message-id : date; bh=GZMJXalNhg4DzoGcUNykF1Rkeeyeumn1nfWOGoxdNn0=; b=W4uwXzS0TkTf4zYizoU/TYAHjGBnMm7yPGR7E97Ym0vORXYiYdF6J1Gh7xhu6POTgrD8Mn szYZlRuUMFWYp2k4HKWc/ES88NHVK1kC/p56bRiheiRsQxhUmxuBVznGvVGi+20UQviuOLxE H/yIcUXPalgJTUjvuTKwvNnZJFw73FuFZH6J8Hjg+NMz1jj2uQoWkJlUFs0/YX6YVMn6kUNu +b7UpXgMu7cgTf9k+LwAC1yeD2wYyi9zJwbNxRG7IJMoe2LvrI1qUEVS9KFhj09l1I/iL8sJ 3zk6Qbe9MKdcOYnju9wBvqDCt7lf442AB52ccIjLqXVx6vKh5kgivlpA==
- Feedback-id: 149811m:149811acx33YQ:149811sMl6DXVwfb
In testing macOS Big Sur, I am finding that chronyd has been broken by Apples aggressive use of their (undocumented) timed daemon.
Even when automatic updating is disabled in the Date&Time control panel, timed will still make adjustments to the system clock, adding spurious offsets of up to 0.5 secs. It appears to be doing based on some internal idea of the current time - it is not sending any packets to port 123
I have been unable to find a way of preventing timed from launching as it is under the control of System Integrity Protection (SIP). Disabling SIP is NOT an option.
I have submitted a 'Feedback' report to Apple about this, but they are notoriously unresponsive. If anyone on the list is able to suggest a workaround I'd be most grateful.
Bryan Christianson
bryan@xxxxxxxxxxxxx
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.