fcron 3.0.4 uses wrong times for next execution of jobs
Submitted by Bram Schoenmakers on 11 February, 2008 - 20:37.
I noticed that my cron jobs were not being run since I upgraded from FCron 3.0.3 to 3.0.4. Running
kill -SIGUSR2 `pidof fcron` && less /var/log/syslog
confirmed this: some (daily) jobs were scheduled for next month. Some jobs even had their next execution time in the past. Something got hosed.
Fortunately, it's not hard to fix this. For every user run as root:
fcrontab -z username
to reschedule all your jobs. It's weird, this shouldn't have happened in the first place.