[mythtv-users] Leap second again??

[Keith Pyle]

This evening, I found my mythbackend system running at full CPU on all 
cores.  It was the leap second problem - again.  According to dmesg on 
this system, it got a leap second inserted just before 0000Z Aug 1:

[202139.171571] Clock: inserting leap second 23:59:60 UTC

This system is running ntp synchronized to a stratum 2 time server (at a 
large university).

Has anyone else seen this today?

The prior workaround resolved the problem:

date -s "`date`"

Keith