On 10/02/15 21:01, Brian Inglis wrote: > Use "ntpq -c rv" to check the leap second file has been updated and > a pending leap second recognized: > > $ ntpq -crv > associd=0 status=0419 leap_none, sync_uhf_radio, 1 event, leap_armed, <<< > version="ntpd [email protected] Jul 30 11:55:08 (UTC+02:00) 2012 (2)", > processor="x86", system="Windows", leap=00, stratum=1, precision=-21, > rootdelay=0.000, rootdisp=0.455, refid=GPS, > reftime=d884e05f.b1f7560d Tue, Feb 10 2015 19:54:07.695, > clock=d884e06a.5c64e486 Tue, Feb 10 2015 19:54:18.360, peer=14134, tc=4, > mintc=3, offset=0.033, frequency=0.900, sys_jitter=0.037, > clk_jitter=0.019, clk_wander=0.000, tai=35, leapsec=201507010000, <<< > expire=201512280000 <<<
I confirm that the ntpq method works. So impatient types who can't wait for the (reportedly daily) check mentioned by Harlan can use that to activate the new leapseconds file immediately and without restarting the daemon. _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
