Re: Build broken on NetBSD and FreeBSD

2016-10-17 Thread Hal Murray
> Fixed, I think. I don't have a *BSD test system. Seems happy. Thanks. > But in ntpd, the ntp_adjtime() calls never touch the time member. The minor > mistake I made in introducing ntp_adjtime_ns() was to try to scale the > Linux-specific time member as though it exists portably and ntpd us

Re: ntpq: cruft/doc

2016-10-17 Thread Eric S. Raymond
Hal Murray : > > 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

Re: no_sys_peer

2016-10-17 Thread Hal Murray
strom...@nexgo.de said: > With only three candidates in the clocklist that's likely the reason it > doesn't pick a system peer. You'll want to set the tos minclock to a higher > value, I'd suggest maybe two times the minsane value. Thanks. I think that's the problem. -- These are my opinions

Re: Build broken on NetBSD and FreeBSD

2016-10-17 Thread Eric S. Raymond
Hal Murray : > OpenBSD has an adjfreq similar to adjtime. /me looks. Maybe not any more; OpenBSD manual search didn't find it. I did find this with a more general search: http://www.manualpages.de/OpenBSD/OpenBSD-5.0/man2/adjfreq.2.html But something is screwy here. OpenBSD URL, but FreeBSD b

Re: Build broken on NetBSD and FreeBSD

2016-10-17 Thread Hal Murray
e...@thyrsus.com said: > Maybe not any more; OpenBSD manual search didn't find it. ... > But something is screwy here. OpenBSD URL, but FreeBSD banner on the page. > Methinks I smell bit-rot. Looks clean on my system: int adjfreq(const int64_t *freq, int64_t *oldfreq); DESCRIPTION

Re: ntpq: cruft/doc

2016-10-17 Thread Hal Murray
e...@thyrsus.com said: > Harder than CSV, where unless someone is being conscientious (and it's > certainly not required in in RFC 4180) you get no self-descriptive clues at > *all*? Er...no. Ah. Sorry. A chunk of context got lost in this discussion. You are talking about the general case.

The JSON driver

2016-10-17 Thread Eric S. Raymond
Hal Murray : > > I can't figure out what you're recommending here, and I want to because I > > believe in taking you seriously even when I think you've just said something > > actually *silly* for the first time in recorded history. Cleaning up the > > parsing code in the driver? Changing the way

Re: ntpq: cruft/doc

2016-10-17 Thread Gary E. Miller
Yo Hal! On Mon, 17 Oct 2016 03:22:42 -0700 Hal Murray wrote: > Is there a good library/package to do the parsing? Do we want to add > another library to the list of requirements? In PHP it is built in. Reading or writing JSON is a one line function call. To write, you just take a nested obje

Re: ntpq: cruft/doc

2016-10-17 Thread Eric S. Raymond
Gary E. Miller : > > Is there a good library/package to do the parsing? Do we want to add > > another library to the list of requirements? > > In PHP it is built in. Reading or writing JSON is a one line function call. > > To write, you just take a nested object and tell PHP to write it as > JS

Proposal - drop the GPSD JSON driver

2016-10-17 Thread Eric S. Raymond
I have come to think the best thing to do about the GPSD/JSON driver is just remove it. This note explains why. Please reply with agreement, disagreement, or comment. One brute fact is that this driver works poorly, if at all. See these tracker issues: https://gitlab.com/NTPsec/ntpsec/issues/5

Re: Proposal - drop the GPSD JSON driver

2016-10-17 Thread Gary E. Miller
Yo Eric! On Mon, 17 Oct 2016 18:28:22 -0400 (EDT) e...@thyrsus.com (Eric S. Raymond) wrote: > I have come to think the best thing to do about the GPSD/JSON driver > is just remove it. This note explains why. Please reply with > agreement, disagreement, or comment. Disagree. The defaults are b