Have you thought about logging and/or printout for debugging?
We have DEBUG and DPRINTF. I almost never use them because the signal to
noise is so low - it prints stuff from all over but I'm only interested in
one small corner.
I occasionally add various msyslog lines when I'm chasing a bug a
I often use DEBUG_MRA_FOO, and then use judgement and taste as to leave it
in or not.
I use "is it worth writing the documentation for it" as part of deciding to
leave it in or not, and also "am I absolutely sure I have characterized and
fixed this bug such that I'm sure it's fixed, and will not r
Yo All!
Hwne did ntpq start doing ths?
ntpq> sysinfo
Unknown variable. Trying one at a time.
associd=0 status=0418 leap_none, sync_uhf_radio, 1 event, no_sys_peer,
system peer:127.127.28.1:123
system peer mode: client
leap indicator: 00
stratum:
> What does this mean, when did it start, and why?
>Unknown variable. Trying one at a time.
I think I added that a long time ago. (several/many months)
The idea is backward compatibility with older versions of ntpd after we added
something to one of the commands that prints a cluster of in
Yo Hal!
On Fri, 19 May 2017 12:28:06 -0700
Hal Murray wrote:
> > What does this mean, when did it start, and why?
> >Unknown variable. Trying one at a time.
>
> I think I added that a long time ago. (several/many months)
>
> The idea is backward compatibility with older versions of ntp
> OK, but why bother the user with the low lever details? UNless you are
> debugging?
No good reason one way or the other. I was happy that it started printing
out stuff again.
Some sort of feedback seems appropriate. Maybe it should print something
like "(not available)" for the slots the
Yo Hal!
On Fri, 19 May 2017 13:00:19 -0700
Hal Murray wrote:
> > OK, but why bother the user with the low lever details? UNless you
> > are debugging?
>
> No good reason one way or the other. I was happy that it started
> printing out stuff again.
Yes, that was progress.
> Some sort of f
> Not useful unless it tells also you what variable was not available.
Yes. I was thinking of something like:
abc: True
foo: (not available)
xyz: 13
> Also, maybe should need a 'verbose' option (-v) before it is output.
The catch with that is that the default doesn't tell you that you ar
Yo Hal!
On Fri, 19 May 2017 13:19:26 -0700
Hal Murray wrote:
> > Not useful unless it tells also you what variable was not
> > available.
>
> Yes. I was thinking of something like:
> abc: True
> foo: (not available)
> xyz: 13
Works for me.
> > Also, maybe should need a 'verbose' opti
