Just looking through the logs and noticed a lot of cron errors that I haven’t seen before. This is being logged every minute:
Tue Mar 31 10:21:00 2026 cron.err crond[4670]: line sleep 70 && touch /etc/banner && reboot
Tue Mar 31 10:22:00 2026 cron.err crond[4670]: wakeup dt=60
Tue Mar 31 10:22:00 2026 cron.err crond[4670]: file root:
Tue Mar 31 10:22:00 2026 cron.err crond[4670]: line sleep 70 && touch /etc/banner && reboot
Tue Mar 31 10:23:00 2026 cron.err crond[4670]: wakeup dt=60
Tue Mar 31 10:23:00 2026 cron.err crond[4670]: file root:
Tue Mar 31 10:23:00 2026 cron.err crond[4670]: line sleep 70 && touch /etc/banner && reboot
I put this line in Scheduled Tasks on my Linksys e8450s to reboot them back when we were having the “kiss of death” issues:
40 1 * * 0 sleep 70 && touch /etc/banner && reboot
Each WAP (5 total) was scheduled to reboot after 1:00am
Each WAP on OpenWRT on was scheduled 10 minutes apart so finicky wireless IOT clients could home and re-home as they went through the schedule. I can probably remove this task now but it has seemed to help some funky IOT clients.
What is wrong with the cron entry?