Gary, Hal, thanks for the prompt replies.
- compiling gpsd fresh would make it use *that* date as a pivot
- The system time being correct *before* gpsd invocation would give it a clue
I seem to remember this being discussed in detail, lots of detail, on the list. I sort of thought the above two safety nets were in place.
Q1: What is your recommendation?
On an ntp issue, I have these two lines:
refclock shm unit 1 prefer refid PPS flag4 1 prefer # minpoll 0 maxpoll 5
# refclock shm unit 0 refid GPS time1 0.650 flag4 1 # minpoll 1 maxpoll 5
Note I commented out the second. I recall discussion that this would give me a top-of-second lock, but not use the GPS for a "count of seconds". This is not happening, ntpd jumps on start to 1999.
Q2: How can I use PPS from gpsd, yet not the absolute time?
Thanks,