Periodic spike in offset for pps
doug.curtis at world-mail.org
Tue May 5 19:41:11 UTC 2020
On Tue, May 5, 2020 at 3:30 PM Gary E. Miller via users <users at ntpsec.org>
> Yo Doug!
> On Tue, 5 May 2020 15:27:07 -0400
> Doug Curtis <doug.curtis at world-mail.org> wrote:
> > On Tue, May 5, 2020 at 2:34 PM Gary E. Miller via users
> > <users at ntpsec.org> wrote:
> > > Yo Doug!
> > >
> > > On Tue, 5 May 2020 14:08:26 -0400
> > > Doug Curtis via users <users at ntpsec.org> wrote:
> > >
> > > > I can't think of anything else to look for or try.
> > >
> > > The next places to look:
> > >
> > > crontab -l
> > > ls -l /etc/cron.*
> > They are stock Raspbian buster installs so there weren't any cronjobs
> > that I enabled. The fake-hwclock job is enabled in cron.hourly so
> > I'm disabling that.
> Are you sure? Can you share your "crontab -l"?
> > I'm trying not to change
> > too much at a time so I can (hopefully) narrow it down. I just have
> > to be patient.
> Softly softly catch monkey.
Here is the crontab -l output:
root at rpi-gps3:~# crontab -l
no crontab for root
root at rpi-gps3:~# crontab -l -u ntp
no crontab for ntp
root at rpi-gps3:~# crontab -l -u doug
no crontab for doug
I may have stumbled on to the issue though. When reviewing the running
processes, I noticed systemd-timesync was running. I know the howto says
to disable it but I assumed (insert your favorite saying about "assume"
here) clockmaker did that for me. A quick "systemctl disable
systemd-timesyncd.service --now" fixed that. I've gone ahead and done that
on all three Pis so I will see what the results of that reveal.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users