Re: ntpq: cruft/doc

e...@thyrsus.com said: >> CSV is readable by eye without a lot of effort. JSON is close to encrypted. > Say *what*? Uh, I can only conjecture that you don't have a lot of actual > experience with JSON. I admit that "encrypted" is an exaggeration, but the signal-noise is pretty low. Yes,

Re: ntpq: cruft/doc

Yo Hal! On Sun, 16 Oct 2016 13:50:28 -0700 Hal Murray wrote: > g...@rellim.com said: > > I was unaware of RFC 4180, and it mandates CRLF as line ending, not > > the \n that I used. I just pushed a fix to this. Someone familiar > > with RFC4180 should check the format

Re: ntpq: cruft/doc

g...@rellim.com said: > And I can't count the number of times people have asked me what the units > are because they can't figure it out. You should not have to read pages of > docc to find the current units. But I shouldn't have to waste valuable screen real estate to tell you what the units

Re: ntpq: cruft/doc

g...@rellim.com said: > I was unaware of RFC 4180, and it mandates CRLF as line ending, not the \n > that I used. I just pushed a fix to this. Someone familiar with RFC4180 > should check the format is correct. My guess is that's for network traffic rather than local files. If you make a

Re: ntpq: cruft/doc

Gary E. Miller : > And I can't count the number of times people have asked me what the > units are because they can't figure it out. You should not have to read > pages of docc to find the current units. > > Check out chronyc, they do a lot of things much better than ntpq. I

Re: Progress on pyntpq

Hal Murray : > > e...@thyrsus.com said: > > I don't have any pressing things to do right now ... > > What about the broken shared-key crypto? > > What about peer not working? Those are both fallout from Daniel's refactoring of the protocol machine. Daniel told me over

Re: ntpq: cruft/doc

Yo Eric! On Sun, 16 Oct 2016 15:14:19 -0400 "Eric S. Raymond" wrote: > > Many CSV files have a comment line on top with the field names. > > Good idea. Gonna be *mandatory* for anybody generating CSV in our > pond. Also strict conformance to RFC4180, at pain of my extreme

Progress on pyntpq

Hal and Gary talking about improving ntpq refocused my attention. I don't have any pressing things to do right now (that's good - that means our hard work has brought the code close to a 1.0 state) so I took another whack at adding some capabilities to pyntpq in order to scope the job of turning

Re: ntpq: cruft/doc

Hal Murray : > > >> The first question is What does "mobilize" mean? > > Is that a rhetorical question? > > No, unfortunately, that's a serious question. I think it has some fine-print > meaning that I don't yet understand. Damn, I was afraid you were going to say

Re: ntpq: cruft/doc

Hal Murray : > > e...@thyrsus.com said: > > About CSV, while I'm not opposed to it we have a practice guideline to use > > JSON for machine-parseable output. One reason is that JSON is better at > > being self-describing - the field names give you clues that CSV doesn't.

Re: ntpq: cruft/doc

>> The first question is What does "mobilize" mean? > Is that a rhetorical question? No, unfortunately, that's a serious question. I think it has some fine-print meaning that I don't yet understand. If it wasn't for this discussion, I would assume it meant something like create a peer

Re: no_sys_peer

Hal Murray writes: > I'm seeing things like this: > remote refid st t when poll reach delay offset jitter > == > 0.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.001 >

Re: Build broken on NetBSD and FreeBSD

Hal Murray : > ../../libntp/machines.c:92:5: error: 'struct timex' has no member named 'time' > ../../libntp/machines.c:101:5: error: 'struct timex' has no member named > 'time' Fixed, I think. I don't have a *BSD test system. Sorry about the belated response, my

Re: ntpq: cruft/doc

g...@rellim.com said: >> If you were starting over, what would you do? I think there are two >> parts to that question. One is the on-wire API. > I think we are stuck with that part. RFC's right? There is nothing that says we can't add new stuff. I've been happy with the shift from mode 7