ntpd should ignore the leap second flag from upstream servers when "leapfile" is configured, but you should update the leap second file before it expires (twice a year)
http://support.ntp.org/bin/view/Support/ConfiguringNTP#Section_6.14. On Thu, Jan 3, 2013 at 4:34 AM, <[email protected]> wrote: > > The NTP servers for my environment sync off of 0-3.us.pool.ntp.org and we > experienced a leap second jump on all of our servers: > > 2012-12-31T23:59:59.730993+00:00 localhost kernel: Clock: inserting leap > second 23:59:60 UTC > > This triggered on some systems without an upgraded kernel the linux hrtimer() > bug which caused CPU spikes across my environments. Happy New Years! > > If I understand it correctly the problem is that certain pool servers are > incorrectly reporting the leap=01 incorrectly? As the latest IERS bulletin > specifies a leap second was NOT to be introduced. > > What is the recommended approach to ensure this doesn't incorrectly happen > again? Once a server receives a leap=01 from an upstream server will it leap > no matter what? > > David, would it be possible to get the flags your sending to ntpq to check > for the leap second flag in your program so we can run them using ntpq on a > linux system ? I'd like to setup a monitor for this condition in our > environment. > _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
