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
Michael
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
