On 2015-02-10 10:51, Jan Ceuleers wrote:
On 10/02/15 18:19, Harlan Stenn wrote:
[email protected] writes:
Either I have missed it, or it is not there. My question is 'does ntpd
have to be restarted after a new leapseconds.list file has been
downloaded?'
No. The code looks for an updated file (daily, I think, more often as
we get closer to an expiration).
See check_leap_file() in ntpd/ntp_util.c .
I've also experimented with using an ntpq :config command to force the
daemon to re-read the leapseconds file, and that also seems to work.
That is: strace shows that the daemon does indeed read the file upon
receiving the :config command from ntpq, but I haven't verified anything
beyond that.
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 <<<
This is from previous Meinberg stable as new release does not recognize PPS.
--
Take care. Thanks, Brian Inglis
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
