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
Hi, Kiss--
Try mailto:questions@lists.ntp.org>>; BCC:ing
.
leap=00 means it's not primed to announce a leap second; if
you wanted to test in more detail, set the date ahead to 2015-6-30
and see whether pending leap second announcement shows (leap=01).
Regards,
--
-Chuck
On May 28, 2015, at 7:
