On Aug 23, 2017, at 10:07 AM, Eric S. Raymond via devel <devel@ntpsec.org>
wrote:
>
> #55: ntpd refclock GPSD_JSON just stops working.
>
> I am unhappy with this driver. I believe - as this bug demonstrates -
> that it's too crappy to ship if we want to establish and maintain a
> reputation for trouble-free operation.
>
> It's an unusual case - the feature that brings it closest to working
> right is marked experimental, and it's redundant with the SHM driver
> because GPSD feeds the SHM driver quite happily. In fact, the JSON
> parsing overhead means the latency and jitter of this driver is
> necessarily inferior to delivery via SHM.
>
> Thus, I think the best thing to do about it would be do simply delete it
> and shed the defect exposure, redirecting users to GPSD+SHM. And
> if that going to happen, it needs to happen *now* - that is, before
> 1.0 implies a promise that it will be stable and maintained.
What about GPSd/NTPSec systems that do not support SHM as required by
GPSd/NTPSec? (Are there any? macOS? Others?)
Thanks,
Frank
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
