Here's more information. As you both suggested, gpsd is feeding bad time to
chronyd.
Starting chrony with the -s option, it still sets the clock to 1999-08-22.
Presumably the drift file had the time set incorrectly in a previous run:
$ cat /var/lib/chrony/chrony.*
72.210307196.256213
1
On Mon, Dec 12, 2016 at 06:14:29AM -0800, Bill Unruh wrote:
> I am also trying to remember-- does the shm truncate the most significant bits
> of the time. For the full time to ns, one would need about 64 bits. Is the shm
> time slots big enough to hold the full time?
Yes, there are two fields, on
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/
On Mon, 12 D
On Thu, Dec 08, 2016 at 04:47:03AM +, Brian Kuschak wrote:
> I'm trying to set up something simple. I want chrony to grab NMEA time as
> soon as it's available, and then sync to PPS. This system (BBB) has no
> battery-backed RTC and no network access.
>
> When the time is initially correct
