Comment 5 for bug 1429427

Figured I'd give it a quick google for this weirdness and stumbled upon this report. Confirmed it, but then started doubting if it actually is cron that's causing this weirdness. So I put a simple strace on my freshly restarted cron with strace -f -p <pid> -s 1000 2>&1 | grep 'CRON\[' and left this running for half a day. Guess what? You can see cron logging like it should, no jumping around. But then when I look at the actual syslog again, I see the cron entries jumping around... So that makes one question syslog somehow... No time yet to dive into that though...