Yo Hal! On Fri, 23 Mar 2018 14:52:31 -0700 Hal Murray via devel <devel@ntpsec.org> wrote:
> > I want my clock not stuck in 2134. -g alone does not fix that.
>
> Back to the beginning. Where does 2134 come from?
The raspberry pi has no RTC. When it starts cold, the time may well be
in 1969. Somehow, not sure how, that becomes 2134. Then gpsd uses that
as the GPS epoch, and things go downhill from there...
> > 'tos minsane 3' fixes it, unless I'm offline, which is pretty
> > common for RasPi.
>
> If you are getting bogus time from a local source and you want to
> work offline, you are pretty much screwed.
Chicken and egg. The local GPS is giving good time, just does not
know the proper epoch.
In the default ntpd case with the addition of external chimers, ntpd
gets the wrong answer.
At a minimum the doc can be improved, or an FAQ added, to avoid this
common issue.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpZoeiF9upDU.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
