Hal Murray :
>
> e...@thyrsus.com said:
> >> hp58503a should probably be hpgps. It works for several devices.
> > OK. Can you enumerate some other devices so I can list them in the header
> > comment and on the driver page?
>
> The documentation already mentions the Z3801A. There are a lot of
cbwie...@gmail.com said:
> I was thinking of setting up associations using the DNS lookup code. If the
> mechanism for adding new pool servers was blocking on the DNS call but
> asynchronous to the rest of the daemon, I was figuring to call the lookup
> with the name provided by the server direct
On Mon, Jun 27, 2016 at 3:47 PM, Hal Murray wrote:
>
> cbwie...@gmail.com said:
> > How are pool entries added when the service decides it needs more?
>
> There is some background stuff that roughly says "need more?", and if so
> fires off the DNS lookup.
>
>
> > Would it be possible to leverage
cbwie...@gmail.com said:
> How are pool entries added when the service decides it needs more?
There is some background stuff that roughly says "need more?", and if so
fires off the DNS lookup.
> Would it be possible to leverage this code for adding all servers specified
> by name?
Probably n
e...@thyrsus.com said:
> An argument for "json", maybe. But not a really compelling one, because
> GPSD defined the protocol and anything else emitting it would probably be
> emulating GPSD deliberately.
I think I prefer JSON for the same reason I like SHM.
I think the real question is does the
Clark B. Wierda :
> IIRC, GPSD NG uses JSON over a socket. Is this restricted to GPSD, or is
> the JSON general enough to be used by any similar source?
It's general enough to be used by any similar source. While that wasn't one
of my design objectives, it's almost implied by something else I was
On Mon, Jun 27, 2016 at 2:49 AM, Gary E. Miller wrote:
>
> Since you opened the door...
>
> > |shm| T | Shared Memory Driver
> > |gpsd | T | GPSD NG client protocol
>
> I think that leads to confusion since they both, at least for now,
> come from gpsd. And until the gpsd_j
On Mon, Jun 27, 2016 at 12:21 AM, Eric S. Raymond wrote:
> The new refclock directive is implemented and documented. This has
> had some large consequences.
>
>
Great!
I'll echo Hal on the desirability to be less specific when we can.
I think we should try to have the options be as descriptive
A question:
How are pool entries added when the service decides it needs more?
Would it be possible to leverage this code for adding all servers specified
by name? The DNS cost would be the same. This only difference is the name
used for the query.
Once a server is associated, the IP is used.
e...@thyrsus.com said:
>> hp58503a should probably be hpgps. It works for several devices.
> OK. Can you enumerate some other devices so I can list them in the header
> comment and on the driver page?
The documentation already mentions the Z3801A. There are a lot of them in
the ham/hacker co
Yo Eric!
On Mon, 27 Jun 2016 05:16:15 -0400
"Eric S. Raymond" wrote:
> > Maybe: gpsd_shm, and gpsd_json. Or: shm and json.
> There is in theory a better case for calling "gpsd"
> something else, but in practice I think JSON is sufficiently flexible
> that we'll never have a variant that's truly
e...@thyrsus.com said:
> Which reminds me: an addition I'm considering is adding "offset" as a
> synonym for time1 or time2, whichever one usually sets an offset for time
> reported from the unit. Only., I'm not clear which it should be; either it
> varies by driver or I'm not understanding the do
Eric S. Raymond writes:
> Which reminds me: an addition I'm considering is adding "offset" as a
> synonym for time1 or time2, whichever one usually sets an offset for
> time reported from the unit.
The documentation is quite unclear on this and I'm not sure I'd trust
each driver to do exactly the
On 2016-06-26 23:49 -0700, Hal Murray wrote:
> $ ./waf --list
> --- building host ---
> The cache directory is empty: reconfigure the project
That looks like a regression I will look at it this morning, strange.
Amar.
___
devel mailing list
devel@ntps
e...@thyrsus.com said:
> More suggestions like this, please.
bps may not be enough. There is also the parity and stop bits, but I don't
think they are fiddled much.
The HP driver uses one mode bit to switch from whatever the default is to a
different baud rate and parity. It may be simpler t
Hal Murray :
> How does your new stuff handle multiple instances of a refclock type?
So far it's only cosmetically different from the old syntax. The
refclock directive has the combined options of the server and fudge
directives - in fact they're parsed by the same code and the same
subproductio
e...@thyrsus.com said:
>> --refclock=irig,nmea,pps,hp58503a,shm,gpsd
> I'm not seeing a problem here. Isn't it trvial to get those names from,
> e.g., https://docs.ntpsec.org/latest/refclock.html ?
The problem is not to "get the names", it's to translate an old number to the
new name. You may
Hal Murray :
> > Can you show me an example of this sort of script?
>
> How do you build things for your collection of systems? Do you really type
> the configuration in by hand each time? Do you use --refclock=all?
Usually it's --refclock=all.
> Here is a fragment that I translated by hand:
e...@thyrsus.com said:
> I don't think shm needs to change at all. It says what it is - data coming
> over System V shm, which defines its own format by the shared structure
I like SHM. I think there are non-gpsd sources of SHM data.
I have no strong preferences for gpsd vs json.
--
These a
How does your new stuff handle multiple instances of a refclock type?
For a test case, I suggest a USB driver in addition to a HAT. Try both
NMEA/PPS as well as both SHM and various combinations.
The JSON driver uses the high bit of the unit to enable/disable the PPS.
The NMEA and HP driver
Gary E. Miller :
> Since you opened the door...
>
> > |shm| T | Shared Memory Driver
> > |gpsd | T | GPSD NG client protocol
>
> I think that leads to confusion since they both, at least for now,
> come from gpsd. And until the gpsd_json driver has sane, documented,
> defa
Hal Murray :
> But there is lots more room in that column. I think it will hold a worst
> case IPv4 numerical address.
>
>
> remote refid st t when poll reach delay offset jitter
> ==
> HP5850
> Can you show me an example of this sort of script?
How do you build things for your collection of systems? Do you really type
the configuration in by hand each time? Do you use --refclock=all?
Here is a fragment that I translated by hand:
--refclock=irig,nmea,pps,hp58503a,shm,gpsd
--
The
Hal Murray :
> It's handy if you are updating a script.
Can you show me an example of this sort of script?
--
http://www.catb.org/~esr/";>Eric S. Raymond
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/de
Hal Murray :
> 1010 ./waf configure
> 1011 ./waf build
>
>
> [ 74/206] Compiling ntpd/ntp_intercept.c
> ../../ntpd/ntp_control.c: In function âctl_putpeerâ:
> ../../ntpd/ntp_control.c:2319:8: error: âstruct peerâ has no member named
> âprocptrâ
>if (p->procptr != NULL) {
>
Hal Murray :
> e...@thyrsus.com said:
> > and the
> > noun/verb "fudge" is reserved for the two time offset options.
>
> Why? What's the difference between a flag that gets set to 0 or 1 and a time
> that gets set to a number?
When I hear the term "fudge factor" I think of a number used to ad
e...@thyrsus.com said:
> and the
> noun/verb "fudge" is reserved for the two time offset options.
Why? What's the difference between a flag that gets set to 0 or 1 and a time
that gets set to a number?
> There will be a *limited* open period for bikeshedding about the driver
> names.
hp58
But there is lots more room in that column. I think it will hold a worst
case IPv4 numerical address.
remote refid st t when poll reach delay offset jitter
==
HP5850 .GPS.0
It's handy if you are updating a script.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
29 matches
Mail list logo
