Description of problem: When I create a new cron (using vi) in /etc/cron.d the cron does not get picked up. If I wait for a couple edit the file again, then save it, it will finally get picked up. Version-Release number of selected component (if applicable): Have tried this on RHEL 3.6, 4, 4.2, 4.3, 4.4 How reproducible: see description above Steps to Reproduce: 1. create new cron in /etc/cron.d/ with vi 2. watch the /var/log/cron file, it won't get "reloaded" 3. edit the file again and save it 4. the new file will finally get "reloaded" Actual results: Expected results: new cron should get picked up when first created. Additional info:
Another way I've been able to solve the problem is wait at least 1 minute then run 'touch /etc/cron.d'
If you don't like crontab -e, then I recommend work around: vi /var/spool/cron/root I try reproduce and jobs from cron.d didn't work for me at all. I'll look at it.
crontab -e is for when you want specific users to have crons. We (as well as most people) prefer to keep system crons in the /etc/cron* directories. (In reply to comment #2) > If you don't like crontab -e, then I recommend work around: > vi /var/spool/cron/root > I try reproduce and jobs from cron.d didn't work for me at all. > I'll look at it.
I shouldn't have to wait, go back, touch it. What happens if (like most of my day) I'm extremely busy and forget to go back and touch the file. A very important task may not run. I shouldn't have to worry whether crond picked up the changes, it should just work. (In reply to comment #1) > Another way I've been able to solve the problem is wait at least 1 minute then > run 'touch /etc/cron.d'
Can't reproduce bug. Jobs in /etc/cron.d/ are loaded imediatelly, but jobs aren't run. Do you have some options? I have: rpm -q vixie-cron anacron crontabs vixie-cron-4.1-20_EL anacron-2.3-32 crontabs-1.10-7 Which versions do you have?
Here's what I'm running rpm -q vixie-cron anacron crontabs vixie-cron-4.1-44.EL4 anacron-2.3-32 crontabs-1.10-7
I fix it for devel. If I'll fix it for RHEL-4, would you mind test it for me?
I was investigating about this problem. My jobs won't run, if I forget to type in /etc/crontab or /etc/cron.d/* username. The cron isn't complainig, that's the only problem, which I can avoid.
I'm closing this bug for long inactivity. If the problem still persist please reopen this bug.