lockclock runtime option

[Eric S. Raymond]

Achim Gratz via devel <devel at ntpsec.org>:
> Well, it turns out ntpq has regressed from classic and doesn't
> understand at least some of that syntax anymore:
> 
> Classic> /usr/sbin/ntpq -c 'rv 0 offset'
> offset=-0.023122
> 
> NTPsec~> ntpq -c 'rv 0 offset'
> server=0 status=0415 leap_none, sync_uhf_radio, 1 event, clock_sync,
> version="ntpd ntpsec-1.1.3+ 2019-01-21T16:51:20Z (git rev 6c029ef4c)",
> processor="armv7l", system="Linux/4.14.79-v7+", leap=00, stratum=1,
> precision=-19, rootdelay=0.0, rootdisp=1.18, refid=NavS,
> reftime=dff33c08.97fbf9ea 2019-01-23T19:16:24.593Z,
> clock=dff33c15.430042c4 2019-01-23T19:16:37.261Z, peer=48728, tc=4, mintc=0,
> offset=-4e-05, frequency=-0.816528, sys_jitter=0.000144, clk_jitter=0.000171,
> clk_wander=2.7e-05
> ntpq: standard-mode lookup of offset failed, Name or service not known
> ntpq: ndp lookup failed, Name or service not known

File a bug on the tracker please.  Should be easy to fix

Entertaining that nobody noticed this before.  Reinforces my theory that
a lot of the more obscure ntpq features are never uses.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.