Leap second tonight

Majdi S. Abbas msa at latt.net
Wed Dec 31 23:27:40 UTC 2008

On Wed, Dec 31, 2008 at 04:41:39PM -0600, Kevin Day wrote:
> 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.

	One note, if you're using ntpd along with an HF receiver and the
CHU reference driver, you'll either need to manually retune your receiver 
to 7850 kHz or update your ntpd.

	As of approximately one hour ago, CHU has moved from 7335 kHz,
where it has been for several decades up to 7850 kHz due to increasing
shortwave broadcast interference.

	Also note that many reference clocks, including GPS derived ones, 
do not handle leap seconds correctly, so it may be a while before your 
reference clocks stabilize.

	Happy New Year!


More information about the NANOG mailing list