-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@daily @hourly etc not run #15
Comments
I can confirm this is still an issue 3 years later. |
Would be nice to see support for these. as well as @reboot |
The problem is that the manual mentions the options but they do not work: As a workaround add something like this in your system crontab file: # SYSTEM HOURLY/DAILY/WEEKLY/MONTHLY FOLDERS |
The issue is that for aliases like @hourly, @daily, etc. any point in time (minute, hour, day of month, month: * * * * ) will be allowed for processing in SynchronizeFile() (database.c:448) and the actual execution of the job only depends on the "frequency" (i.e. 60x60 for hourly, 24x60x60 for daily, etc.).
To make the aliases work, I added the following two lines to SynchronizeFile() (database.c:458): Then the debug messages look like: But @henri62's workaround (explicitely using time tables instead of aliases) will certainly do. |
closes dubiousjim#15 Signed-off-by: Mario Haustein <[email protected]>
After merging of #3, my @daily @hourly etc jobs are not run. I've reverted back to 6186237 and they are run again.
The text was updated successfully, but these errors were encountered: