Red Hat Bugzilla – Bug 3539
cron(8) does not appear to rescan crontabs.
Last modified: 2008-05-01 11:37:50 EDT
Cron jobs entered via "crontab -l" don't appear to take
effect unless crond is stopped and restarted.
"crontab -l" is for listing current jobs, not for entering
new jobs. Do you mean "crontab <filename>" or "crontab -e",
I have tested installing a new personal crontab entry, and
crontab properly rescanned it without touching the cron daemon.