[181740] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: REMINDER: LEAP SECOND

daemon@ATHENA.MIT.EDU (Chris Adams)
Wed Jul 1 14:17:09 2015

X-Original-To: nanog@nanog.org
Date: Wed, 1 Jul 2015 13:17:06 -0500
From: Chris Adams <cma@cmadams.net>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <1167688244.5050.1435769040800.JavaMail.mhammett@ThunderFuck>
Errors-To: nanog-bounces@nanog.org

Once upon a time, Mike Hammett <nanog@ics-il.net> said:
> v5 is 2.4, v6 3.3.5 

Don't know why a 3.3.5 kernel would have deadlocked; don't think there
are any known issues that would cause that, unless there are Mikrotik
specific patches that caused the problem.

I believe the bug from the 2008 leap second was present in kernels in
2.4 up through 2.6.26 (although Red Hat at least patched it in their
older version long-term support kernels).

-- 
Chris Adams <cma@cmadams.net>

home help back first fref pref prev next nref lref last post