On Thu, Aug 09, 2018 at 11:54:54AM -0400, Greg Wooledge wrote:
On Thu, Aug 09, 2018 at 04:15:36PM +0100, Darac Marjal wrote:Additionally, from http://doc.ntp.org/current-stable/ntpq.html#rv (rv allows one to read the offset for a particular association directly), "Note that time values are represented in milliseconds and frequency values in parts-per-million (PPM)."Where do I even start....
It sounds like you should start with a user/client/desktop oriented time program. There's no reason for most users to be running ntpd in 2018. If you're running a server syncing to a PPS source or somesuch then you need ntpd. But at that point you're going to have to learn a lot of domain-specific jargon to do that thing, at which point the ntpd documentation is fine. If you want something that's fire and forget, then install openntpd or systemd-timesyncd and call it a day.
Mike Stone