Description of problem:
when load crontab into the in-memory database of crond, the process_crontab function in database.c will check if the mtime of a crontab is changed. if the mtime is not changed, it will skip load of the crontab file even when it was actually changed.
this will cause changes not take effect before a restart of crond.
Version-Release number of selected component (if applicable):
hard to reproduce, but possible.
Steps to Reproduce:
1.make change to user crontab, say at 10:00:30 AM
2.crond will load change of step 1 at the first second of the next minute, say: 10:01:01 AM
3.make change to user crontab again, at the same second, but just several millisecond after step 2, say: 10:01:01 AM 500ms.
new cron entries added in step 3 will not run by crond
changes in step 3 should take effect
This is now fixed in the newest upstream release. If a crontab is modified in the same second it is being read by crond, the crond will re-read it on the next wake-up.