July 1, 2012
10:14 p.m.
It was a kernel race condition (and subsequent live lock) after ntpd notified the clock subsystem of the coming leap second ( http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-...) The joys of fine grained locking :) Cheers, Nick. -- Sent from my phone, thus the relative brevity :) On Jul 2, 2012 5:45 AM, "Antoine Pitrou" <solipsis@pitrou.net> wrote:
On Sun, 1 Jul 2012 21:11:25 +0200 Guido van Rossum <guido@python.org> wrote:
So would "supporting" the leap second in Python have made any difference?
No. These look like system (kernel?) bugs.
Regards
Antoine.
_______________________________________________ Python-ideas mailing list Python-ideas@python.org http://mail.python.org/mailman/listinfo/python-ideas