<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div class="default-style">
John Thurston <john.thurston@alaska.gov> wrote:
<br>> Eric Raymond's HOWTO for a stratum 1 server
<br>> <https://www.ntpsec.org/white-papers/stratum-1-microserver-howto/> uses
<br>> /gpsd/ to provide the GPS data to ntpsec.
<br>
<br>> It explains the decision with this:
<br>
<br>> /If you are already familiar with ntpd and wonder why this recipe uses
<br>> gpsd through SHM rather than ntpd’s native refclock 20 GPS driver, the
<br>> answer is this: when refclock 20 is configured to use 1PPS, it mixes
<br>> in-band time data with 1PPS in a way that causes it to behave badly, and
<br>> possibly get rejected as a falseticker, when 1PPS is only occasionally
<br>> available./
<br>
<br>I don't see any significant-looking changes in the commits
<br>messages except cleanups and refactors until earlier this year.
<br>(which would not be in 1.2.1)
<br>
<br>> The history notes on the page indicate it was first published late in
<br>> 2016, and last updated in the middle of 2018. There has been a lot of
<br>> water under the bridge, and many changes to ntpsec since then.
<br>
<br>> My question is this: Four years on, is this still a valid reason to
<br>> prefer /gpsd/ to using the 127.127.20.0 and 127.127.22.0 reference clock
<br>> drivers for GPS and PPS?
<br>
<br>Support for devices that talk things other than NMEA 0183 and
<br>slightly atypical PPS wiring isn't enough.
<br>
<br>John Thurston <john.thurston@alaska.gov> later revised:
<br>> My question is this: Four years on, is this still a valid reason to
<br>> prefer /gpsd/ and /refclock shm/ over /refclock nmea/ and /refclock pps/ ?
<br>
<br>> In my mind, using the /refclock shm/ and also running /gpsd/ is more
<br>> complication than relying on the two /refclock/ already available. But
<br>> if the latter is prone to unexpected failures, then there are good
<br>> reasons to accept the complication of the former.
</div>
<div class="default-style">
</div>
<div class="default-style">
> (Apologies if this is a duplicate message. I have not received my copy
<br>> of the message I sent earlier this month, nor has it appeared in the
<br>> web-archives, nor have I received any reply to my query to the
<br>> users-owner email address.)
<br>
<br>Messages on the mailing list tend to take too long to arrive. I
<br>think the delay is up to two months at this point (post through
<br>California is faster). We should keep the posts list mirrored.
</div>
<div class="default-style">
</div>
<div class="default-style">
JamesB192 -- Not on the team anymore
</div>
<div class="default-style">
Last person hanging around.
</div>
</body>
</html>