Hal Murray via devel writes:
>> the assumption you are suffering from GPS rollover issues
>
> WNRO seems unlikely. That would be off by 20 years. This case if off by 2.
Did you even read what I wrote? This is ntpd assuming a WRNO and
warping the time forward in a misguided attemt at fixing it.
> the assumption you are suffering from GPS rollover issues
WNRO seems unlikely. That would be off by 20 years. This case if off by 2.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailm
Udo van den Heuvel via devel writes:
> Garmin gps18x on the serial port with USB power.
> With just $GPGGA and $GPRMC enabled, so where did it find that weird date?
If you had the clockstats file enabled, you would be able to see what
message ntpd received at that point. Since you have RMC enable
On Fri, Jul 3, 2020, at 6:05 AM Udo van den Heuvel via devel
wrote:
>
> On 03-07-2020 15:00, Hal Murray wrote:
> >> How can I avoid this from happening again?
> >
> > That isn't enough info to figure out what happened. Somehow, ntpd thought
> > the
> > time was way off, and you had the -g switch
On 03-07-2020 15:00, Hal Murray wrote:
>> How can I avoid this from happening again?
>
> That isn't enough info to figure out what happened. Somehow, ntpd thought
> the
> time was way off, and you had the -g switch on that allowed it to take big
> jumps. If you turn off the -g switch, ntpd w
> May 18 10:06:48 boombox ntpd[2055]: CLOCK: time stepped by 59097600.478559
> May 18 10:06:48 boombox ntpd[2055]: CLOCK: time changed from 2020-07-03 to
> 2022-05-18
> We're running a fairly recent git version of ntpsec: ntpsec-1.1.9-0.fc31.x86_6
> 4 on Fedora 31 on kern
On 03-07-2020 10:34, ASSI via devel wrote:
> Udo van den Heuvel via devel writes:
>> May 18 10:06:48 boombox ntpd[2055]: CLOCK: time stepped by 59097600.478559
>> May 18 10:06:48 boombox ntpd[2055]: CLOCK: time changed from 2020-07-03 to
>> 2022-05-18
>
> That's
Udo van den Heuvel via devel writes:
> May 18 10:06:48 boombox ntpd[2055]: CLOCK: time stepped by 59097600.478559
> May 18 10:06:48 boombox ntpd[2055]: CLOCK: time changed from 2020-07-03 to
> 2022-05-18
That's why you don't trust the GPS time until you know it has a good
lo
time stepped by 59097600.478559
May 18 10:06:48 boombox ntpd[2055]: CLOCK: time changed from 2020-07-03
to 2022-05-18
May 18 10:06:48 boombox ntpd[2055]: INIT: MRU 10922 entries, 13 hash
bits, 65536 bytes
(cut)
We're running a fairly recent git version of ntpsec:
ntpsec-1.1.9-0.fc31.x86_64 on F
