1 Jul
2012
1 Jul
'12
12:30 p.m.
Hello Russell, On Sun, 2012-07-01 at 18:57 +1000, Russell Coker wrote:
On Sun, 1 Jul 2012, Alan Harper <alan@aussiegeek.net> wrote:
No general suggestions, but this could be the leap second bug. See http://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-second-high-cpu-a nd-the-fix/
Thanks. I used date(1) to set the date and then CPU use suddenly dropped.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679723
There's already a Debian bug, I should have checked the BTS before asking on the list.
But then the rest of us would not have had the news. I have been reading things about leap seconds, and now knowing that it can have a real impact is of value, along with that you cleared the matter by using date. Regards, Mark Trickett