From: Rich Wales
I may have found the answer to my own question.
I added "time1 619315200" to the "refclock" line in my ntp.conf file,
and restarted ntpsec, and it appears to be sane once again.
(And, of course, 619315200 = 7,168 days = 1,024 weeks.)
Rich Wales
ri...@richw.org
====================================
Thanks for reporting that, Rich. I haven't seen that issue with either the
GPS18 LVC, or the GPS18x LVC, but neither have been powered down. Were
yours running continually? Anyway, I love the fix!
I'm running reference NTP here, and noted that with a type 22 PPS driver,
the "prefer" must include the type 20 NMEA driver. With the problem
pending, I had hoped that using an e.g. Internet source for coarse time
might have been enough, and had commented out the NMEA source, but it
appears not to be the case. The PPS was never used (but it appeared in the
billboard).
Cheers,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-tay...@blueyonder.co.uk
Twitter: @gm8arv
_______________________________________________
time-nuts mailing list -- time-nuts@lists.febo.com
To unsubscribe, go to
http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com
and follow the instructions there.
