> I'm curious if any don't simply step the clock. Back in 2005, I had a NetBSD system that stalled the clock for a second. http://www.megapathdsl.net/~hmurray/leap-second/tsc.png There is a slight slope to the flat part of the line, so the clock isn't stopped, just ticking very slowly.
If I was writing that sort of code, it would advance one smallest tick on each call to get the time. Many data base systems freak out if time goes backwards. I assume they are setup to pass the slew-only flag to ntpd. I think that will take a bit over 1/2 hour to catch up a second. It probably depends upon the normal drift of the system. Google has hacked their internal NTP servers so that they speed up starting several hours before the leap happens. That's a small enough change that the clients just track it. Just before the leap, the clients are 1/2 second fast. Just after the leap they are 1/2 second slow. A few more hours and everything is back to normal. -- These are my opinions. I hate spam. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
