Description of problem:
When executing "service crond reload" it responds ""Reloading cron daemon
configuration: " and then sends a HUP signal to the crond daemon. The problem
is that the crond daemon doesn't reload it's configuration upon receiving HUP as
many daemons do. It's man page states that it closes and reopens it's log files
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add a line like "* * * * * root /bin/touch /tmp/foo" to /etc/crontab.
2. Execute "service crond reload".
3. Wait a minute.
4. Look for /tmp/foo file - it never gets created.
5. Execute "service crond restart".
6. Wait a minute.
7. Look for /tmp/foo file - now it's there.
/tmp/foo is not created unless crond is restarted.
/tmp/foo gets created within a minute
Since there is no signal that will cause crond to reload its configuration, the
reload command cannot be made to work without making it a redundant version of
the restart command. Suggest simply removing the reload command.
Removing this might break scripts that depend on it - but those scripts weren't
Created attachment 148358 [details]
Patch to remove "reload" option from service file
I had similar problem in devel. I added some patches from devel to FC-6 last
week, so try update and let me know. I try it and works for me.
The problem was proper reading jobs from all queries.
Use standart paths like /etc/cron.* or use crontab -e.
/etc/crontab is part of package crontabs and his primary use isn't scheduling
jobs as you've mentioned.