Red Hat Bugzilla – Bug 253536
No way to avoid or adjust delay
Last modified: 2007-11-30 17:12:13 EST
I like my daily cron jobs to run at the same time on all my systems (it is much more convenient if log rotation happens as close to midnight as possible for example). Somewhere along the line (I don't see where in the changelog or in any release notes), an arbitrary delay (based on hostname) was added to the daily, weekly, and monthly cron directories. There is no way to override it that won't be changed in an update. There is no configuration read in the file, and it is not marked %config in the spec, so I cannot reliably avoid this undocumented delay. The delay should be calculated once and stored in a sysconfig file (rather than calculated every time). Then it would also be possible to manually set the delay to 0 (and not have to worry about a future update overwriting my change).
Delays in all cron.{daily,hourly,...} should solve this issue #110894. You're right, I'll think about configuration.
I'm sorry, that isn't issue but bugzilla 110894
Thank's for report, it will be soon in update.
crontabs-1.10-15.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
I see the sysconfig file, but it doesn't look like it is actually referenced by anything. Also, as long as configuration is being added, I would suggest the delay be configurable (not just "on/off"). Something like: [ -f /etc/sysconfig/crontab ] && . /etc/sysconfig/crontab if [ -z "$DELAY" ]; then # Calculate the delay ... fi sleep $DELAY exit 0 Then have a default sysconfig that just has a commented out DELAY=1 line (as an example).
crontabs-1.10-15.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
The issue has not been addressed at all; please read comment #5.
I agree you're solution is "nicer". I'll push it to update process.