| [chrony-dev] chronyd broken on macOS Big Sur |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx, chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-dev] 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=J+sRXRdf/q1wzbXncO+flxsRT6 oVfZuI/0mByY6/acTu/SSdheMwWhDjYpBUK0Na8ztufu6wQAkqGBfTABCBZTlzFjOjsAWuJNjXtEk rNbmvFEA6YDrlOjnxWNJpOLwixGilDXzTFqSXiaU+TCwdqdNW0MFp7+LH+to5vfUrH4kPyYQPcdzw 6mtyiYq3ttEkmOO5chl+Jy/STlgyx4yAgqIgleOuq4YvCBNMoc3rOizSLXsyDW+vBLrs2guG97RKx LWLSZj3f1N0ourGk5UgUTSm+di4+wNkNAMyoqj//yT1GQ5/qchimUWYhEl/EN8cYO2BL303WGS3vH c8rQ/Ndw==;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=whatroute.net; i=@whatroute.net; q=dns/txt; s=s149811; t=1595023523; h=from : subject : to : message-id : date; bh=GZMJXalNhg4DzoGcUNykF1Rkeeyeumn1nfWOGoxdNn0=; b=So2j3PAorRO+yDTFpYO0eL/ktMvN74ongLGWak0N+S6yWfqt+3gr4kG0KSntJtcaa5xzEG FjNb84ZrPAke6deJQBn2zUarnQVqM15dAUSBP2T4kGTejvO9anIZdWh63qhUSOBjyMa/7NBU YYpMFgNiwg924VIn4pWI27+bUdX9ToQ0rnzOSiWlCvZhm4pUrAv3KU6XPwl6qXEB+Lcfqkpp AEKcGO/+YixQ9piumTpHR8zRiYbrSmHIf8dC12iubiEm6kVus9kc0VoxnmgEa3Js373i2wQ+ pJZvyOZRNeubnmsaAqt5hjaQG0Gk0yEJySatWqKvu5/WVMAjS1u+15FQ==
- 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-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.