[gpsd-users] GPS reporting wrong time to SHM

[Alexander Carver]

Using the shared memory of gpsd 3.4 to feed ntpd data from a SiRF 
receiver, I've noticed that it is sending the wrong time by one second. 
 This happened after the leap second occurred on June 30/July 1.

The GPS receiver is showing the UTC offset properly as 16 seconds 
(verified via SiRFDemo) but it seems to be getting an additional second 
added because ntpd is receiving a time stamp one second in the future 
(an offset of 17).  I'm having to compensate in ntpd by subtracting an 
additional second with the fudge command.  However, when polling by 
JSON, it seems to report the proper time.

Has this been addressed in the later versions?