Re: Use of pool servers reveals unacceptable crash rate in async DNS

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

Re: The new refclock directive is implemented and documented

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

Re: The new refclock directive is implemented and documented

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

Re: The new refclock directive is implemented and documented

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.

Re: The new refclock directive is implemented and documented

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

Re: Use of pool servers reveals unacceptable crash rate in async DNS

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.

Re: The new refclock directive is implemented and documented

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

offset: time1 or time2

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

Re: The new refclock directive is implemented and documented

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

Re: waf list shouldn't need to be configured

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

Re: New ntpq peers chops refclocks to 6 characters

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

Re: waf --list needs to show old numbers as well as new names

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

waf --list needs to show old numbers as well as new names

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

Re: Our testing sucks

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) { ^

Re: The new refclock directive is implemented and documented

Yo Eric! On Mon, 27 Jun 2016 00:21:45 -0400 "Eric S. Raymond" wrote: > The new refclock directive is implemented and documented. Cool. > There will be a *limited* open period for bikeshedding about the > driver names. Since you opened the door... > |shm| T |

waf list shouldn't need to be configured

$ ./waf --list --- building host --- The cache directory is empty: reconfigure the project $ -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel

Re: head broken if no refclocks

Hal Murray : > after a simple ./waf configure > > [murray@fed raw]$ ./waf build > --- building host --- > Waf: Entering directory `/home/murray/ntpsec/raw/build/host' > [1/5] Processing ntpd/ntp_parser.y > [2/5] Compiling build/host/ntpd/ntp_parser.tab.c >

Re: Our testing sucks

Hal Murray : > > 1007 ./waf configure --refclock=20,22 --enable-debug-gdb > 1008 ./waf build > 1009 gdb ./build/main/ntpq/ntpq > > (gdb) run -p > Starting program: /home/murray/ntpsec/raw/build/main/ntpq/ntpq -p > Missing separate debuginfos, use: dnf