Note: This behaviour was observed on a Pi B+; it was not observed on a Pi 2.
I happened to have top up while doing the bonded Nic test and noticed that the load was awfully high. Then the following popped up:
Cron pretty much has the CPU pegged.
Once I saw this, I wondered what on Earth cron could be doing that was so intensive. So I looked in /var/spool/cron/crontab and it was empty.
A few minutes later this followed:
It was still roughly eating 1/2 the CPU time.
So I rebooted and observed the same behaviour.
I then did a sudo service cron stop and started my tests from scratch…..
