lockclock runtime option

[Achim Gratz]

Hal Murray via devel writes:
> It's easy to add new variables.  Old ntpq may not show them in any of its 
> packaged printout like peers or kerninfo, but you can get them by asking 
> explicityly.

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


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables