Leap second tonight

Thu Jan 1 01:35:49 UTC 2009

It looks like clepsydra hasn't been updated:

     address         ref clock     st  when  poll reach  delay  offset    disp
-~192.5.41.40      .USNO.            1   194  1024  377    41.1    5.19    38.2
-~130.207.244.240  .GPS.             1    68  1024  377    23.1   11.09     1.3
 ~127.127.7.1      127.127.7.1       7    53    64  377     0.0    0.00     0.0
+~198.60.22.240    .GPS.             1   436  1024  377    65.7    7.09    32.5
 ~204.123.2.5      .GPS.             1   182  1024  377    80.4  1011.4    24.9
+~67.128.71.76     .CDMA.            1   178  1024  377    16.8   10.85    79.2
+~18.26.4.105      .CDMA.            1   562  1024  377     8.4    7.90   235.8
-~209.81.9.7       .GPS.             1   170  1024  177    79.9   16.96   170.8
*~209.51.161.238   .CDMA.            1  1019  1024  377     3.9   10.13     2.5
-~204.152.184.72   .GPS.             1   697  1024  377    75.0    1.81     3.2
+~18.145.0.30      .PSC.             1  1737  1024  376    10.0    8.52   297.1

Quick, someone call DEC.

Seriously, clepsydra is one of the older ntp servers out there, and hasn't dealt with the leap second correctly.

-----Original Message-----
From: Kevin Day [mailto:toasty at dragondata.com] 
Sent: Wednesday, December 31, 2008 5:42 PM
To: NANOG list
Subject: Leap second tonight

Just a reminder that there's a leap second tonight.

Last time I watched for what happened on 01/01/2006, there was a  
little bit of chaos: http://markmail.org/message/cpoj3jw5onzhhjkr?q=%22kevin+day%22+leap+second+reminder+nanog&page=1&refer=cnkxb3iv7sls5axu

I've been told that some of the causes of these problems are fixed on  
any reasonably recent ntp distribution, but just in case, you might  
wanna keep an eye out if you're seeing any weirdness. The worst damage  
I'd heard from anyone after that event was their clock being  
significantly off for several hours.

-- Kevin