On Sat 14 Mar 2020 at 21:49:43 (-0400), Gene Heskett wrote: > > In an attempt to reduce the load on my time servers and to mitigate the > jumps in system time that can play heck with timing errors of a running > LinuxCNc session, I have installed an ntp client on a raspbian buster, > and I think I have told it to listen to iburst from this machine. All > my other machine are setup similar and appear to be working ok. > > But the pi with an identical config is still not synching.
Is this something to do with the Pi not having a hardware clock? IOW when it boots up, it doesn't have a clue what time it is. I've read that you should run ntpd -g -q on the Pi, having first stopped its daemon/service (according to how you're running it, sysvinit/systemd). This allows a time jump from 4004 BC or whatever it boots up at. Then restart the daemon/service. Cheers, David.
