Dec 31 23:59:59 howww-a kernel: Clock: inserting leap second 23:59:60 UTC But but but, the last leap second was Jun 30! Does anyone else see this? This has appeared on the 2/2 of RHEL5 machines I've checked so far. Google is being as dickish as google has been for the past couple of years and returns results not relevant to my search at all. -- Tim Connors
On Thu, Jan 3, 2013 at 11:55 AM, Tim Connors <tconnors@rather.puzzling.org> wrote:
Dec 31 23:59:59 howww-a kernel: Clock: inserting leap second 23:59:60 UTC
But but but, the last leap second was Jun 30! Does anyone else see this? This has appeared on the 2/2 of RHEL5 machines I've checked so far.
Google is being as dickish as google has been for the past couple of years and returns results not relevant to my search at all.
Chances are you got hit by an upstream-NTP server from a higher statum sending you data with leap-second flag set. The upstream server should be notified. The current IERS Bulletin for leap-second announcements has specifically said: "NO leap second will be introduced at the end of December 2012." http://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat -Matt
participants (2)
-
Matt Davis -
Tim Connors