[181436] in North American Network Operators' Group
Re: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Chris Adams)
Wed Jun 24 12:33:08 2015
X-Original-To: nanog@nanog.org
Date: Wed, 24 Jun 2015 11:33:06 -0500
From: Chris Adams <cma@cmadams.net>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <20150624160500.GC7191@puck.nether.net>
Errors-To: nanog-bounces@nanog.org
Once upon a time, Majdi S. Abbas <msa@latt.net> said:
> "Total and utter carnage" is a bit of a stretch. Linux hosts
> that ran applications dependant on nanosleeps needed reboots. Note
> that this wasn't an issue in 2009, because the poorly tested change in
> question hadn't yet been made to the Linux kernel.
In 2009, there was a different problem. If the system was under
sufficient kernel-related load (such as disk I/O), the kernel's attempt
to print an informational message that a leap second had been added
caused a kernel deadlock, immediately killing the system.
I don't remember any widespread Linux-related leap second issues before
that though.
--
Chris Adams <cma@cmadams.net>
