Hi Miroslav
> On 27/08/2020, at 8:10 PM, Miroslav Lichvar wrote:
>
> I guess it's also possible that the ntp_adjtime() call doesn't
> actually do anything. You could try changing the frequency in larger
> steps, e.g. 100 ppm every minute and see if it has any effect on the
> offset reported by
On Thu, Aug 27, 2020 at 07:52:28PM +1200, Bryan Christianson wrote:
>
> > On 27/08/2020, at 6:52 PM, Miroslav Lichvar wrote:
> >
> > You could start with the test/kernel/ntpadjtime.c program, modified to
> > very slowly change the frequency of the clock, e.g. 1 ppm per minute.
> > If you run at
> On 27/08/2020, at 6:52 PM, Miroslav Lichvar wrote:
>
> You could start with the test/kernel/ntpadjtime.c program, modified to
> very slowly change the frequency of the clock, e.g. 1 ppm per minute.
> If you run at the same time chronyd with the -x option and a short
> polling interval, you
On Thu, Aug 27, 2020 at 11:41:44AM +1200, Bryan Christianson wrote:
> It worked!!! I left the daemon running for over 30 minutes and it held the
> system time to +/- 5 usecs of NTP, (mostly better than +/- 1usec). The timed
> daemon did NOT change the clock at all during this test and chronyd
> On 24/08/2020, at 12:29 AM, David Bohman wrote:
>
> 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.
>
I think I have ruled out timed as being the cause of the
Bryan,
On Thu, Aug 20, 2020 at 10:32 PM Bryan Christianson
wrote:
>
> > On 29/07/2020, at 12:28 AM, David Bohman 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
David, thanks for the feedback
> On 29/07/2020, at 12:28 AM, David Bohman 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
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.
On Fri, Jul 17, 2020 at 3:05 PM Bryan
