On Tue, Aug 21, 2012 at 10:34 UTC, Santi Saez <sa...@woop.es> wrote: > Is there any proper way to configure ntpd in order to ignore leap second > announcements from remote NTP servers? > > I have tried configuring leapfile/ntpkey_leap features in order to use local > configuration, but if the remote NTP server announces a leap second it's > forwarded to the client, and that's what I want to avoid.
Configuring a leapfile works here, using 4.2.7, to force a local leap configuration that ignores upstream leap bits. I expect the same is true of 4.2.6. I'm afraid I have no information on 4.2.4 or earlier leap behavior, as I haven't used 4.2.4 in a number of years. Cheers, Dave Hart _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
