leapseconds are easy

[tau_iota_mu_c]

Going to have to reset the time on a lot of servers tomorrow! automount here on my machines at home were all spinning at 30% with this strace:

[pid 11844] futex(0x7ff0a854c1a0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 11844] futex(0x7ff0a854c164, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1677805273, {1341147745, 698117000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 11844] futex(0x7ff0a854c1a0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 11844] futex(0x7ff0a854c164, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1677805275, {1341147745, 698307000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)

(opera and firefox were a bit crazy too).

Turns out that the fix is to stop ntp, and set the current time to the current time, then restart ntp:

http://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-second-high-cpu-and-the-fix/
http://www.techopsguys.com/2012/06/30/synchronized-reboot-of-the-internet/
and
http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-during-a-leap-second

And this only gives further ammunition to those idiots wanting to get rid of UTC leapseconds. Stop writing buggy software, people!