Yo Ian!
On Mon, 24 Apr 2017 10:35:25 -0500
Ian Bruene wrote:
> On 04/24/2017 08:43 AM, Eric S. Raymond wrote:
> > One possible technical blocker: I don't know if async DNS lookups
> > are doable from Python.
>
> Doesn't look like async DNS is possible in stock Python. There is a
> library wi
Ian Bruene :
>
>
> On 04/24/2017 08:43 AM, Eric S. Raymond wrote:
> >One possible technical blocker: I don't know if async DNS lookups are doable
> >from Python.
>
> Doesn't look like async DNS is possible in stock Python. There is a library
> with python bindings to do it (*another* dependency)
On 04/24/2017 08:43 AM, Eric S. Raymond wrote:
One possible technical blocker: I don't know if async DNS lookups are doable
from Python.
Doesn't look like async DNS is possible in stock Python. There is a
library with python bindings to do it (*another* dependency), and there
is always the
Achim Gratz :
> > You don't have the asynchronous option either. The protocol is lockstep and
> > reverse-lookup on an address can cause long client-side stalls.
>
> I can already say I just want the IP addresses. I can get those from
> the (possibly remote) ntpd very fast and send off the reve
Yo Achim!
On Tue, 07 Feb 2017 20:56:36 +0100
Achim Gratz wrote:
> Hal Murray writes:
> > Looks like we are getting into the old precision vs accuracy tangle.
> > Do we have a glossary with useful descriptions?
> > That slot should represent the number of useful bits.
>
> It really doesn't hel
Yo Achim!
On Tue, 07 Feb 2017 20:36:15 +0100
Achim Gratz wrote:
> Gary E. Miller writes:
> >> That slot should represent the number of useful bits.
> >
> > Yup. And in Selsky's case he really does have -30.
>
> Nope.
I disagree.
> The resolution of the numbers is 1ns, the useful digits a
Gary E. Miller :
> Writing up saomething that some will agree with will be relatively easy.
>
> Changing the ntpsec doc and code to match will be nasty.
But probably worth doing.
--
http://www.catb.org/~esr/";>Eric S. Raymond
Please consider contributing to my Patreon page at ht
Hal Murray writes:
> Looks like we are getting into the old precision vs accuracy tangle.
> Do we have a glossary with useful descriptions?
> That slot should represent the number of useful bits.
It really doesn't help that precision, accuracy and resolution have a
number of different meanings dep
Gary E. Miller writes:
>> That slot should represent the number of useful bits.
>
> Yup. And in Selsky's case he really does have -30.
Nope. The resolution of the numbers is 1ns, the useful digits aka
precision of the measurement doesn't extend that far down. That -30
would be equivalent to 931
Yo Eric!
On Tue, 7 Feb 2017 06:16:11 -0500
"Eric S. Raymond" wrote:
> Hal Murray :
> > Do we have a glossary with useful descriptions?
>
> I've saved an email thread by Gary and Achim and was planning to try
> to digest it into a series of entries for our glossary. I might get
> to that toda
Yo Hal!
On Tue, 07 Feb 2017 02:56:24 -0800
Hal Murray wrote:
> g...@rellim.com said:
> > OTOH, prolly best to set it to -30, just for grins. Someday it
> > might matter, or I might have missed something, or just to seem to
> > do the right thing.
>
> Looks like we are getting into the old p
Hal Murray :
> Do we have a glossary with useful descriptions?
I've saved an email thread by Gary and Achim and was planning to try
to digest it into a series of entries for our glossary. I might get
to that today.
I expect you'll be involved in the resulting description up to your
eyeballs. :-)
g...@rellim.com said:
> OTOH, prolly best to set it to -30, just for grins. Someday it might
> matter, or I might have missed something, or just to seem to do the right
> thing.
Looks like we are getting into the old precision vs accuracy tangle.
Do we have a glossary with useful descriptions?
Yo Matthew!
On Mon, 6 Feb 2017 14:30:43 -0500
Matthew Selsky wrote:
> Does the shm driver need any modifications?
> # ntpshmmon
> ntpshmmon version 1
> # Name Seen@ClockReal L
> Prec
> sample NTP0 1486408132.108158719 1486408132.107249611 14
On Wed, Feb 01, 2017 at 02:22:07PM -0800, Gary E. Miller wrote:
> Yo Hal!
>
> On Wed, 01 Feb 2017 14:06:18 -0800
> Hal Murray wrote:
>
> > [I tried to submit an issue, but it was reject as spam.]
>
> Gitlab yesterday found spammers uing their submission system. Their
> cure was worse than the
strom...@nexgo.de said:
> Well, If I know that I'm going to display ten characters wider than usual, I
> can add teo digits of extra precision before I widen the space for the
> hostname by four digits. That sort of intelligence.
All the recent changes have been for the case of no extra command
Eric S. Raymond writes:
> Achim Gratz :
>> Eric S. Raymond writes:
>> > You can't know enough to be "intelligent" before the per-host data
>> > arrives.
>>
>> Well, If I know that I'm going to display ten characters wider than
>> usual, I can add teo digits of extra precision before I widen the sp
Achim Gratz :
> Eric S. Raymond writes:
> > You can't know enough to be "intelligent" before the per-host data
> > arrives.
>
> Well, If I know that I'm going to display ten characters wider than
> usual, I can add teo digits of extra precision before I widen the space
> for the hostname by four d
Eric S. Raymond writes:
> You can't know enough to be "intelligent" before the per-host data
> arrives.
Well, If I know that I'm going to display ten characters wider than
usual, I can add teo digits of extra precision before I widen the space
for the hostname by four digits. That sort of intelli
Achim Gratz :
>> The current code prints out each line as soon as the data is returned from
>> the server. Another approach would be to collect it all so we could scan
>> the
>> column and use the 4th digit if everything would fit.
>
> I'm not sure what the implication of waiting for all data
Hal Murray writes:
> It's so close to working reasonably well without an extra flag that a bit of
> kludgery seems worthwhile.
What I'm saying is that we already have introduced variable field width
in some sense, so the code that prints out the data might just as well
drop all pretenses of deali
strom...@nexgo.de said:
> I don't know how compatible you are trying to stay with the "classic"
> output, but to me it seems you'd be better off with such changes made
> conditional on the use of an option, either a new one or maybe the existing
> '-W' one (which means that the extra space first g
> Is the jitter column header/data supposed to have moved 1 character to the
> right?
Yes. The printout is now 79 characters wide rather than 78.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.
Hal Murray writes:
> I just pushed a fix. Please test.
>
> I bumped the width from 78 to 79. If that screws up, we should document a
> test case. I'm assuming the output supports an 80 character line.
I don't know how compatible you are trying to stay with the "classic"
output, but to me it se
On Sat, Feb 04, 2017 at 01:39:45AM -0800, Hal Murray wrote:
> Good catch. Thanks.
>
> I just pushed a fix. It's the sort of kludge that Eric won't like but I
> don't have a better idea.
Hey Hal,
Looks better.
$ ntpq -pn ; ./ntpclients/ntpq -pn
remote refid st t when pol
Hal Murray :
>
> matthew.sel...@twosigma.com said:
> > We need some backwards compatibility for ntp classic servers. Eg, the
> > server has only microsecond precision. We need to avoid adding trailing
> > zeros that are not actually significant.
>
> Good catch. Thanks.
>
> I just pushed a fi
matthew.sel...@twosigma.com said:
> We need some backwards compatibility for ntp classic servers. Eg, the
> server has only microsecond precision. We need to avoid adding trailing
> zeros that are not actually significant.
Good catch. Thanks.
I just pushed a fix. It's the sort of kludge tha
On Fri, Feb 03, 2017 at 04:24:58AM -0800, Hal Murray wrote:
>
> I just pushed a fix. Please test.
>
> I bumped the width from 78 to 79. If that screws up, we should document a
> test case. I'm assuming the output supports an 80 character line.
>
> There was a space-space before the delay col
Yo Hal!
On Fri, 03 Feb 2017 04:24:58 -0800
Hal Murray wrote:
> I just pushed a fix. Please test.
After 30 seconds of testing, works for me.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 977
I just pushed a fix. Please test.
I bumped the width from 78 to 79. If that screws up, we should document a
test case. I'm assuming the output supports an 80 character line.
There was a space-space before the delay column. I grabbed one of them.
Those 2 extra spaces let me change the widt
Hal Murray :
>
> e...@thyrsus.com said:
> >> Looks like lines from ntpmon are one character shorter than ntpq.
> > They use the same display code - pylib/uril.py::PeerSummary.
>
> I get the same width when run directly on a system, but see the difference
> when ssh-ing into that system.
>
> Th
e...@thyrsus.com said:
>> Looks like lines from ntpmon are one character shorter than ntpq.
> They use the same display code - pylib/uril.py::PeerSummary.
I get the same width when run directly on a system, but see the difference
when ssh-ing into that system.
The refid column and everything t
Hal Murray :
> Right now, I've got a ntpmon window with 5 servers and 4 blank lines after
> the lines that exactly fill the whole line. Have you tried adjusting your
> window for an exact fit?
I have. I did that when testing my change.
> Looks like lines from ntpmon are one character shorter
e...@thyrsus.com said:
>> The current display is 78 characters wide. Is there a good reason
>> not to use the last 2?
> Nope. That's what my previous commit did.
There may be quirks with somebody putting in a line break at exactly 80
rather than waiting to see if the next character is a retu
Hal Murray :
> The current display is 78 characters wide. Is there a good reason not to use
> the last 2?
Nope. That's what my previous commit did.
--
http://www.catb.org/~esr/";>Eric S. Raymond
___
devel mailing list
devel@ntpsec.org
e...@thyrsus.com said:
> Sigh. I'll revert that commit. I don't think there's any horizontal slack
> left in the display, then.
Don't revert. I'll fix it.
The current display is 78 characters wide. Is there a good reason not to use
the last 2?
g...@rellim.com said:
> Hal already updated y
Yo Eric!
On Wed, 1 Feb 2017 23:18:33 -0500
"Eric S. Raymond" wrote:
> Hal Murray :
> > [I tried to submit an issue, but it was reject as spam.]
> >
> > Somebody recently changed things to print out a 4th digit. That
> > made things worse. It was already broken if you had a negative
> > number
Hal Murray :
> [I tried to submit an issue, but it was reject as spam.]
>
> Somebody recently changed things to print out a 4th digit. That made things
> worse. It was already broken if you had a negative number bigger than 1000
> which isn't all that uncommon.
Sigh. I'll revert that commit.
Yo Hal!
On Wed, 01 Feb 2017 16:14:41 -0800
Hal Murray wrote:
> Your version of "nice" conflicts with mine.
I'd love to see what you can come up with.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Ben
> Since it is a string, maybe send something nicer?
The formatting should be done in ntpq.
Your version of "nice" conflicts with mine.
As far as I'm concerned, you can fix ntpq so it has an option to do anything
you want as long as the default doesn't change.
--
PS: My suggesti
>> The printout in ntpq still needs floating point for big numbers.
> Not sure how that would look.
Ugly, but less ugly than the current setup.
In case I wasn't clear, instead of printing "-1234.5678", it should print
"-1234.56".
It's probably simplest to turn it into a string with 4 digits to
Yo Hal!
On Wed, 01 Feb 2017 15:11:42 -0800
Hal Murray wrote:
> The printout in ntpq still needs floating point for big numbers.
Since it is a string, maybe send something nicer? Instead of:
*SHM(1) .PPS.0 l28 377 0. -0.0050 0.0015
-clepsydra.labs. .GPS.
Yo Hal!
On Wed, 01 Feb 2017 15:11:42 -0800
Hal Murray wrote:
> g...@rellim.com said:
> > Eric did that. Also notice the LSB is always zero, which is
> > clearly also wrong.
>
> I just pushed a fix.
>
> That stuff goes from ntpd to ntpq as text. It was 3 digits of
> fraction. Now 6.
Grea
g...@rellim.com said:
> Eric did that. Also notice the LSB is always zero, which is clearly also
> wrong.
I just pushed a fix.
That stuff goes from ntpd to ntpq as text. It was 3 digits of fraction. Now
6.
--
The printout in ntpq still needs floating point for big numbers.
--
These
Yo Hal!
On Wed, 01 Feb 2017 14:06:18 -0800
Hal Murray wrote:
> [I tried to submit an issue, but it was reject as spam.]
Gitlab yesterday found spammers uing their submission system. Their
cure was worse than the disease...
> Somebody recently changed things to print out a 4th digit. That mad
[I tried to submit an issue, but it was reject as spam.]
Somebody recently changed things to print out a 4th digit. That made things
worse. It was already broken if you had a negative number bigger than 1000
which isn't all that uncommon.
ntpq -p
remote refid st t when pol
46 matches
Mail list logo