Hi, Kiss-- Try <questions@lists.ntp.org <mailto:questions@lists.ntp.org>>; BCC:ing <p...@lists.ntp.org>.
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:03 AM, Kiss Gábor <ki...@niif.hu> wrote: > Dear folks, > > I don't want to bother this list with ntpd contiguration problems. > Could you suggest an approriate mailing list where I can get help > with my dozen of old NTP daemons of version 4.2.6p5 and leap second settings? > > > However if you are interested in it, I can tell that the best result > with the latest leap-seconds.3629404800 file and 4.2.6p5 is this: > > $ ntpq -c "rv 0 leap,tai,leapsec,expire" one_of_my_servers > 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. That is strange... > > Thanks > > Gabor > _______________________________________________ > pool mailing list > p...@lists.ntp.org > http://lists.ntp.org/listinfo/pool _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
