<div dir="ltr"><div>Eric,</div><div><br></div><div>I am using the SHM driver , which talks to gpsd. The presence of the "g" suffix causes the line to be ignored.</div><div><br></div><div>root@ntpmon:~/ntpsec# grep refclock /etc/ntp.conf <br></div><div>refclock shm unit 0 refid GPS time1 0.650g flag4 1</div><div>root@ntpmon:~/ntpsec# kill -9 `pidof ntpd` ; ntpd -D 100<br></div><div>root@ntpmon:~/ntpsec# ntpq -pn<br>server=localhost No association IDs returned</div><div><br></div><div>ntpd.log:<br></div><div><br></div><div>2000-01-01T02:23:58 ntpd[20105]: INIT: Using SO_TIMESTAMPNS<br>2000-01-01T02:23:58 ntpd[20105]: IO: Listen and drop on 0 v6wildcard [::]:123<br>2000-01-01T02:23:58 ntpd[20105]: IO: Listen and drop on 1 v4wildcard <a href="http://0.0.0.0:123">0.0.0.0:123</a><br>2000-01-01T02:23:58 ntpd[20105]: IO: Listen normally on 2 lo <a href="http://127.0.0.1:123">127.0.0.1:123</a><br>2000-01-01T02:23:58 ntpd[20105]: IO: Listen normally on 3 eth1 <a href="http://203.123.48.219:123">203.123.48.219:123</a><br>2000-01-01T02:23:58 ntpd[20105]: IO: Listen normally on 4 lo [::1]:123<br>2000-01-01T02:23:58 ntpd[20105]: IO: Listen normally on 5 eth1 [2405:fc00:0:1::123]:123<br>2000-01-01T02:23:58 ntpd[20105]: IO: Listen normally on 6 eth1 [fe80::204:23ff:feb8:1c1e%3]:123<br>2000-01-01T02:23:58 ntpd[20105]: IO: Listening on routing socket on fd #23 for interface updates<br>2000-01-01T02:23:58 ntpd[20105]: INIT: This system has a 32-bit time_t.<br>2000-01-01T02:23:58 ntpd[20105]: INIT: This ntpd will fail on 2038-01-19T03:14:07Z.<br>2000-01-01T02:23:58 ntpd[20105]: PROTO: 0.0.0.0 c01d 0d kern kernel time sync enabled<br>2000-01-01T02:23:58 ntpd[20105]: PROTO: 0.0.0.0 c012 02 freq_set kernel 39.594910 PPM<br>2000-01-01T02:23:58 ntpd[20105]: PROTO: 0.0.0.0 c016 06 restart<br>2000-01-01T02:23:58 ntpd[20105]: NTSc: Using system default root certificates.<br></div><div><br></div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">-- <br>Sanjeev Gupta<br>+65 98551208 <a href="http://www.linkedin.com/in/ghane" target="_blank">http://www.linkedin.com/in/ghane</a></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Aug 17, 2019 at 1:41 AM Eric S. Raymond via devel <<a href="mailto:devel@ntpsec.org">devel@ntpsec.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I've just pushed a change that interprets a 'g' suffix on a clock time1<br>
fudge option as an instruction to add the number of seconds in a <br>
1024-week GPS era. There can be more than one g. Using this, you can<br>
compensate for era rollover in old GPS devices.<br>
<br>
Credit to James Browning for the idea. It's actually done at the<br>
scanner level, so it will work for other double-valued options such<br>
as the time2 fudge - not that I expect that to be used.<br>
<br>
If you have a GPS old enough to require wraparound compensation,<br>
please test; I don't think I do anymore.<br>
<br>
I've also updated the driver documentation, pointing out where this<br>
option is likely to be of use, and the NEWS file.<br>
<br>
Mark: once we've tested this it might merit a point release.<br>
-- <br>
<a href="<a href="http://www.catb.org/~esr/" rel="noreferrer" target="_blank">http://www.catb.org/~esr/</a>">Eric S. Raymond</a><br>
<br>
You know why there's a Second Amendment? In case the government fails to<br>
follow the first one.<br>
-- Rush Limbaugh, in a moment of unaccustomed profundity 17 Aug 1993<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@ntpsec.org" target="_blank">devel@ntpsec.org</a><br>
<a href="http://lists.ntpsec.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ntpsec.org/mailman/listinfo/devel</a><br>
</blockquote></div>