Bryan,
On Thu, Aug 20, 2020 at 10:32 PM Bryan Christianson <
bryan@xxxxxxxxxxxxx> wrote:
>
> > 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.
Yes, I can understand that. I run all my macOS systems with SIP disabled.
>
> 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 prefer to have the Preference UI continue to work. I do that by having my own wrapper script in /usr/local which generates the appropriate pool command from macOS configuration into a file which is included by the main chrony.conf.. Of course, the chrony daemon must continue to be known to launchd as <whatever> so the Preference Pane can find it.
>
> 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.
Are you certain that that timed is remaining suspended? That launchd is not resuming it? I don't have a machine which will run Big Sur, so I cannot investigate it myself.
David Bohman