[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] Direct GPS support in ntpd makes me nervous

From: Eric S. Raymond
Subject: Re: [gpsd-dev] Direct GPS support in ntpd makes me nervous
Date: Tue, 22 Oct 2013 18:53:35 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

Harlan Stenn <address@hidden>:
> ntpd has had direct driver support for a Very Long Time, pre-dating
> gpsd.  This includes support for a number of non-GPS devices.

Yeah.  And it makes some sense for you to directly support things like
time-radio receivers. 

Though I have to say that I think the modularity advantages of getting
core ntpd out of the hardware-support business entirely look good to
me.  You have an as-near-as-dammit zero-latency symbiont interface
through shared memory; why not use it for everything rather than
bundling driver code for a dozen obsolete devices into the image every
client user runs?

If it were me, I'd break the program apart into ntpd and clockd
pieces.  Leave nptd just doing the aggregation, Byzantine algoritms,
and distribution.  Exile all the hardware management to clockd.  Have
clockd feed ntpd through the shared-memory interface.

> I'm game to identify all of the refclocks that ntpd supports, and if
> gpsd is supporting those refclocks I'll talk to DLM about this and bring
> it up on the appropriate NTP lists for discussion.
> This seems like a reasonable plan to me, and I'd be game to look at the
> chrony pipes to see about including them in ntpd, too.

Good. You can count on close cooperation from me and I'm sure Gary as well.
                <a href="";>Eric S. Raymond</a>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]