Verified - ntpd ignores the year part of refclock timestamps

[Hal Murray]

devel at ntpsec.org said:
> No?  Well, I just did.  Fsck...me...sideways!  It's true.  The reason all
> those old, busted Y2K-afflicted refclocks worked is that ntpd really does
> ignore the year part of clock timestamps. 

The problem I'm interested in is not Y2K, it's GPS rollover.  1024 weeks is 
not an integral number of years.  The day and month are garbage too.

I'm seeing:
  T2199801140539523001053
which is 1998, 01=Jan, 14

---------

I agree this is a mess.  I think we need a flag to go with with the year.  
Then we can update the drivers to provide the year (and set the flag) as we 
get to them.

How many of the GPSD test sets for NMEA have 2 digit years?


-- 
These are my opinions.  I hate spam.