Re: Progress, and a puzzle.

2016-11-04 Thread Eric S. Raymond
Hal Murray : > > > That's the reason for the ntp symlink in ntpq. If you run pyntpq from > > there, import ntp should find that link and all should be well. Is "." not > > on your Python import path? > > That's the right question. Thanks. > > Who is supposed to setup PYTHONPATH? The Python

Re: Progress, and a puzzle.

2016-11-04 Thread Hal Murray
> That's the reason for the ntp symlink in ntpq. If you run pyntpq from > there, import ntp should find that link and all should be well. Is "." not > on your Python import path? That's the right question. Thanks. Who is supposed to setup PYTHONPATH? A raw clone has: pylib/ntpc.so -> ../b

Re: Progress, and a puzzle.

2016-11-04 Thread Eric S. Raymond
Hal Murray : > > Hal, you sould try reinstalling. That version of the Python extension might > > be stale, which *could* trigger the OpenSSL conlict. > > I tried that and it still dies. OK, that's weird. I certainly cannot reproduce it here. > > Try running pyntpq in the ntpq directory. That

Re: Progress, and a puzzle.

2016-11-04 Thread Hal Murray
> Hal, you sould try reinstalling. That version of the Python extension might > be stale, which *could* trigger the OpenSSL conlict. I tried that and it still dies. > Try running pyntpq in the ntpq directory. That's an ntp symlink to the > source-tree location of the libries it needs. That

Re: Progress, and a puzzle.

2016-11-03 Thread Eric S. Raymond
Mark Atwood : > > You could fix that. I'd probably wait until there is a good reason to add > > another command. > > > > At least for the time being, we want the Python implementation of ntpq to > interop with NTP Classic. And even if we manage to land a fixing patch on > NTP Classic, we want to

Re: Progress, and a puzzle.

2016-11-03 Thread Eric S. Raymond
Hal Murray : > > One wonders, for example, why exactly one response (readstats) has a binary > > payload > > My guess is history. It's probably left over from before the mode6/mode7 > stuff got sorted out and Mills decided that mode6 should be all text. That seems plausible. > You could fix th

Re: Progress, and a puzzle.

2016-11-03 Thread Eric S. Raymond
Jason Azze : > On Thu, Nov 3, 2016 at 2:54 PM, Hal Murray wrote: > > > How are you testing things? > > > > I get this: > > > > $ ./ntpq/pyntpq > > Traceback (most recent call last): > > File "./ntpq/pyntpq", line 17, in > > from ntp.packet import * > > File "/home/murray/ntpsec/play/ntpq

Re: Progress, and a puzzle.

2016-11-03 Thread Jason Azze
On Thu, Nov 3, 2016 at 2:54 PM, Hal Murray wrote: > How are you testing things? > > I get this: > > $ ./ntpq/pyntpq > Traceback (most recent call last): > File "./ntpq/pyntpq", line 17, in > from ntp.packet import * > File "/home/murray/ntpsec/play/ntpq/ntp/packet.py", line 16, in >

Re: Progress, and a puzzle.

2016-11-03 Thread Mark Atwood
On Thu, Nov 3, 2016 at 11:54 AM Hal Murray wrote: > > One wonders, for example, why exactly one response (readstats) has a > binary > > payload > > My guess is history. It's probably left over from before the mode6/mode7 > stuff got sorted out and Mills decided that mode6 should be all text. > >

Re: Progress, and a puzzle.

2016-11-03 Thread Hal Murray
> For those of you interested, Mode 6 is now fully documented at docs/ > mode6.txt. It's a strange piece of design - very nearly excellent, but with > a bunch of inconsistencies and odd glitches that spoil the effect. Many thanks. > One wonders, for example, why exactly one response (readstats

Progress, and a puzzle.

2016-11-03 Thread Eric S. Raymond
The Python translation of ntpq is done, modulo one minor feature in mrulist that I expect to have up later today. All commands, including the authenticated ones, are working. The translation has turned up a weird bug in ntpd, however. It turns out that in two mode 6 responses, reslist and ifstat