Off-list Gary referred to a fix being in gpsd 3.20 (released Dec 31, 2019). I saw the note about "Convert all timestamp_t to timespec_t", but can't tell if that is involved in the potential fix. Mike was running GPSD "git head from ~2 months ago", which is later than 3.20. I can't tell whether the two-second error would be fixed by 3.20.
Can anyone explain how GPSD would trigger a 2 second error? On Tue, May 26, 2020 at 12:10 PM Gary E. Miller via devel <[email protected]> wrote: > Yo Steven! > > On Tue, 26 May 2020 11:37:53 -0500 > Steven Sommars via devel <[email protected]> wrote: > > > Any similar observations? Known problems ? > > This was caused by a bug in one version of gpsd. New versions of > gpsd do not have that bug. The exact bug was not found, instead the > entire way gpsd keeps time was changed from doubles to timespec_t. > > Anyone with this problem needs to update their gpsd. > > RGDS > GARY > --------------------------------------------------------------------------- > Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 > [email protected] Tel:+1 541 382 8588 > > Veritas liberabit vos. -- Quid est veritas? > "If you can't measure it, you can't improve it." - Lord Kelvin > _______________________________________________ > devel mailing list > [email protected] > http://lists.ntpsec.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
