9 Commits (02469e4e8eca3dd5cfd42f159175ec536300db33)

Author	SHA1	Message	Date
Kim Alvefur	38c67064b3	mod_cron: Fix recording last task run time #1751 ... The type checks, they do nothing! Observed: Tasks that were supposed to run weekly or daily were running each hour.	4 years ago
Kim Alvefur	98922d54b1	plugins: Prefix module imports with prosody namespace	3 years ago
Kim Alvefur	e0e180aa9d	mod_cron: Allow for a small amount of timer drift ... If the timer activates a bit early then a task might be just a few seconds short of being allowed to run. This would run such a task rather than wait another hour. The value 0.5% chosen so that a weekly task does not run an entire hour earlier than last time.	4 years ago
Kim Alvefur	d48fa1de17	mod_cron: Expose the One Timer via module environment ... This makes it easier to reschedule or otherwise manipulate the timer from e.g. the shell, which is handy for debugging.	4 years ago
Kim Alvefur	8aa16eaec0	mod_cron: Add a 'weekly' job frequency	4 years ago
Kim Alvefur	d6070eea1f	mod_cron: Initialize timestamp of new tasks to start of period ... Makes it more generic so new periods (e.g. weekly etc) can be added easily.	4 years ago
Kim Alvefur	914d3acbd5	mod_cron: Follow convention of imports at the top	4 years ago
Kim Alvefur	6f3409f3f2	mod_cron: Initialize daily tasks so they run around midnight UTC ... Eventually the goal is to have daily tasks run while there is little activity, but that will vary with the server and the usage patterns of its users. This is a start anyway.	4 years ago
Kim Alvefur	630035a369	mod_cron: Initial commit of periodic task runner ... A number of modules now have periodic tasks that need to run, e.g. for cleaning out old messages or files. This has highlighted a need for coordinating and optimizing scheduling of such tasks.	4 years ago