lockclock runtime option

Achim Gratz Stromeko at nexgo.de
Wed Jan 23 20:07:48 UTC 2019


Hal Murray via devel writes:
> Achim said:
>> Well, it turns out ntpq has regressed from classic and doesn't understand at
>> least some of that syntax anymore: 
>
>> 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)", 
> ...
>
> Works for me.  Anything interesting about your setup?

No, just plain stupidity on my side.  I tried to run the command via ssh
and forgot I need to double-quote in this case.

So, lockclock is not known as a system variable of course.


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

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra



More information about the devel mailing list