| Re: [chrony-dev] chronyd broken on macOS Big Sur |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] chronyd broken on macOS Big Sur
- From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
- Date: Fri, 21 Aug 2020 17:31:50 +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:Message-Id:To:Date: Subject:From:Reply-To:Sender:List-Unsubscribe; bh=SYmJt05gjm0WRzD+K4AgTFPhtRXPIqocZX2kX+ED+8E=; b=SymHJ5cQg3jfDRTm6eMxMcm1hs lppUBC0SlgQM+0DjDDFSGai8+G/xs2n5waLj7JAci29rtTg2PaPESn5WvTq6eY852MDjHABbYN3ln V6KlAI/c61Hb2UQ7HPmpHKzeisolHilMdXCs+8g4mW65f6g11RkkE4Yc0nCmsMMzTzT/f1ibxBicL M9SQdS1coWlGRksSO9IWbv38Hhv0rK7ewoXVxbvF3J0ZpZhntxqNxLxjk9kpznbiCsCn/mcaN46EG 89/wHHJv0itvBlUQlPy82TsRGBuFeOcVJuqtAT6n8yt6TBQGAfjabuLqt4vk543lfaqB2npY87shS kYuQ1kUw==;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=whatroute.net; i=@whatroute.net; q=dns/txt; s=s149811; t=1597987924; h=from : subject : to : message-id : date; bh=SYmJt05gjm0WRzD+K4AgTFPhtRXPIqocZX2kX+ED+8E=; b=cSS7vYlQqTmzet8tpe0R1NRl0lhCPKq8tr+g6/S9V+DeSn/XjfBPPg8G2mvXGpZy9e5AGR e5wvhUPgTC/9LYU19Ut3V9nE89Ni/56zCJEf5tS6eUZ5nDK0Z7nRQSmXn/+yzco72c+qdifb 44wxxt0AwVdbUhwZXyW8DjEJVIF/EwzFUdYbK09gIgg0IxdzEn7IOaGvYGmunSgZWVZsgnXM rD2TlEvv1hC9nzaMzZTFCpV2/TeTrYBAAUMNCWnnaE04TkCgI6kBGMjBF7Hty4DbVOfb30J2 /EyzAlSlRUi5WASqzhW6RXO0hE1ewJBnqMZSIKy2QzctWjXkoF0rtNPg==
- Feedback-id: 149811m:149811acx33YQ:149811sjFTcXa-t_
David, thanks for the feedback
> On 29/07/2020, at 12:28 AM, David Bohman <debohman@xxxxxxxxx> wrote:
>
> Why is disabling SIP not an option, at least temporarily? It seems to me that you need to replace the timed service in order to use chronyd at all. You cannot have two daemons running at the same time who both think that they are disciplining the clock.
>
I am reluctant to remove timed with SIP disabled because because it is not something I would like to do on an ongoing basis - i.e after every OS update. Also, I don't want to support end users in disabling SIP and removing timed if they have installed chrony via my ChronyControl application. If there was some way to do it without booting into recovery then I would be happy with that.
Please note, on macOS 10.13, 10.14 10.15 chronyd works very well when:
1. the specified time server in System Preferences/Date & Time is set to a non-existent host.
2. automatica update is disabled in the same System Preferences pane.
I had an idea that if I was to send a SIGSTOP to timed, then that would solve the problem. However, when I tried this from the command line (pkill -STOP timed) something is still messing with the system clock and every minute or so, chronyd is emitting messages about the clock being wrong. This indicates that simply removing timed still won't solve the problem.
I've had zero feedback from Apple in response to my bug report and I'm not sure where to proceed from here. If there are any Mac developers on the list, it might be a good idea to each submit a feedback report in an attempt to get Apple to take notice of the issue. It just doesn't feel right to me that they can take on timekeeping based on, according to Wikipedia https://en.wikipedia.org/wiki/Timed , a standard from the mid 1980s that as far as I am aware is used by no-one else.
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.