diff options
author | Kim Alvefur <zash@zash.se> | 2023-07-30 13:03:40 +0200 |
---|---|---|
committer | Kim Alvefur <zash@zash.se> | 2023-07-30 13:03:40 +0200 |
commit | 3a071d87b8dd5d6d29b79a4166e3ef0fda83df1a (patch) | |
tree | 75cced75a95a6bc7ce7b4989bbddb7a6a21b1dd9 /teal-src/prosody/plugins/mod_cron.tl | |
parent | 4d699626445b5a5b03435732b3cded4057b704c2 (diff) | |
download | prosody-3a071d87b8dd5d6d29b79a4166e3ef0fda83df1a.tar.gz prosody-3a071d87b8dd5d6d29b79a4166e3ef0fda83df1a.zip |
mod_cron: Revert bbd3ac65640d
Maybe it is better to run daily and weekly tasks 'now' on the theory
that people set these things up during times that are appropriate for
maintenance already, so the same time next day or next week might be
fine for periodic cleanup.
Diffstat (limited to 'teal-src/prosody/plugins/mod_cron.tl')
-rw-r--r-- | teal-src/prosody/plugins/mod_cron.tl | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/teal-src/prosody/plugins/mod_cron.tl b/teal-src/prosody/plugins/mod_cron.tl index b71b5f74..357294d6 100644 --- a/teal-src/prosody/plugins/mod_cron.tl +++ b/teal-src/prosody/plugins/mod_cron.tl @@ -56,11 +56,6 @@ function module.add_host(host_module : moduleapi) task.save = save_task; module:log("debug", "%s task %s added, last run %s", task.when, task.id, task.last and datetime.datetime(task.last) or "never"); - if task.last == nil then - -- initialize new tasks so e.g. daily tasks run at ~midnight UTC for now - local now = os.time(); - task.last = now - now % periods[task.when]; - end return true; end |