More on ntpq

[Hal Murray]

It doesn't have a ^C catcher for the printout part of the mru command.  I was 
expecting ^C to stop printing stuff and go back to the main read-a-command 
loop.

---------

>> The mru list is getting printed out oldest first.  I thought you fixed 
that.
> I thought I did too.  Testing...

It still comes out backwards for me.

[murray at glypnod ~]$ ntpq --version
ntpq -126-play 2016-11-06T00:05:45Z
[murray at glypnod ~]$ which ntpq
/usr/local/bin/ntpq
[murray at glypnod ~]$ ll /usr/local/bin/ntpq
-rwxr-xr-x 1 root root 60350 Nov 30 23:13 /usr/local/bin/ntpq
[murray at glypnod ~]$ ntpq -nc mru
Ctrl-C will stop MRU retrieval and display partial results.
lstint avgint rstr r m v  count rport remote address
==============================================================================
  4088   1.00   d0 . 3 4      4 52609 195.37.190.94
   264    282   d0 . 3 3     17 57021 192.11.130.225
   195     94   f0 L 3 4     51 61425 24.15.80.185
   157    262   d0 . 3 4     19   123 135.109.218.198
   154    282   d0 . 3 4     17 45118 131.193.178.43
   154    175   d0 . 3 4     27   123 192.11.69.21
   148    243   d0 . 3 4     20   123 69.20.5.68
    66     64    0 . 4 4     78   123 192.168.1.105
    59     67   d0 . 3 4     75   123 fe80::ba27:ebff:feba:fdfc%2
    54     32    0 . 3 4    156   123 192.168.1.49
    49    250    0 . 3 4     20   123 192.168.1.22
...


[Erics sample]

> That looks newest first.  Either I'm deeply confused or you're running a
> stale version somehow.

I just tried again with a fresh clone.  It's coming out backwards.  So I vote 
that there is a problem on your end.

esr at snark:~/software/ntp-rescue/ntpsec$ ntpq -c mru
Which ntpq is that actually running.  You aren't cd-ed to ntpq so you aren't 
explicitly running your latest build.

--------
[Python version string]

> You're looking at the value of VCS_DATE, which is "The date of the most
> recent commit in true ISO-8601/RFC3339 format, including seconds."

> What do you think should be there instead?

I think I've figured out what is going on.  The "most recent" above is 
misleading.  It means the first one printed out by git log.  So if you have 
un-pushed commits and rebase=true, you get the date from your last commit 
even after pulling many updates.

I'll move the rest of the discussion to another message.

-- 
These are my opinions.  I hate spam.





-- 
These are my opinions.  I hate spam.