Dear folks, I've several old RHEL5 hosts in the NTP Pool with ntpd version 4.2.6p5. I try to manage the leap second coming at end of June but I have partial success only. Now ntpd at least finds the leap-seconds.3629404800 file but I guess it gets confused:
$ ntpq -c "rv 0 leap,tai,leapsec,expire" my_server leap=00, expire=201505281348, leapsec=201501050000, tai=35 $ The expire value is the minute of restarting ntpd, and the leapsec was at 5th of January. Relevant configuration: keysdir /etc/ntp crypto pw a_password $ ls -l /etc/ntp -rw-r----- 1 root ntp 84 Sep 30 2011 keys -rw-r--r-- 2 root root 10384 Apr 10 10:48 leap-seconds.3629404800 lrwxrwxrwx 1 root root 58 May 28 15:40 ntpkey_cert_my_server -> ntpkey_RSA-MD5cert_my_server.3641809254 lrwxrwxrwx 1 root root 53 May 28 15:40 ntpkey_host_my_server -> ntpkey_RSAkey_my_server.3641809254 lrwxrwxrwx 1 root root 23 May 28 15:32 ntpkey_leap -> leap-seconds.3629404800 -rw-r--r-- 1 root root 639 May 28 15:40 ntpkey_RSAkey_my_server.3641809254 -rw-r--r-- 1 root root 626 May 28 15:40 ntpkey_RSA-MD5cert_my_server.3641809254 -rw-r--r-- 1 root root 186 Feb 3 2009 ntpservers -rw-r--r-- 1 root root 0 Nov 26 2009 step-tickers $ grep -v '^#' /etc/ntp/ntpkey_leap | tail -5 3124137600 32 # 1 Jan 1999 3345062400 33 # 1 Jan 2006 3439756800 34 # 1 Jan 2009 3550089600 35 # 1 Jul 2012 3644697600 36 # 1 Jul 2015 Could you suggest what can I try yet? Thanks Gabor _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
