| 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: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 27 Aug 2020 10:10:08 +0200
- Authentication-results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1598515814; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=EQRG2ebrtC3b2JiAXfv7kRApxzO5+3C1c4n0VjgJKkk=; b=KrfUhS7/OmKPRZ3+424cu6RvbLbq8QbfxrnPQPbhpenAaTnG/WVzRjU7KOqc8yRny9dxAY g9fReVUrUNhbIjVsokPPuHnvEtUuSHK5DQPzRCF7ePHi3VUGdV9LRsuby6p+YeywqnAa0L vSxaiMF0rbHuRYCmA8Y7XC4YUNsamt4=
On Thu, Aug 27, 2020 at 07:52:28PM +1200, Bryan Christianson wrote:
>
> > On 27/08/2020, at 6:52 PM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> 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 should see in the tracking log when the
> > offset jumped.
>
> Thank you Miroslav - I'll get on to this tomorrow.
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 chronyd -x. If it looks the same as when you don't
change the frequency, ntp_adjtime() isn't doing anything.
--
Miroslav Lichvar
--
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.