aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar netravnen <1938389+netravnen@users.noreply.github.com>2024-04-03 18:11:36 +0000
committerGravatar Christian Hesse <mail@eworm.de>2024-04-04 21:13:37 +0200
commit1d8347d8ea0b4c16d4a3763e2f73c186da360a01 (patch)
tree48e435e4d8a5fb09c081f99454fe170365d5e4cb
parent444f56f9b44baf8a2553e2e475f796626c5da3ae (diff)
README: add start-time & change interval in scheduler example
Set the interval to once a day, Instead of every 1 hour. Add start-time to start-up. Thereby introducing randomization based on when the user last rebooted there device. As the interval is counted based on last boot time.
-rw-r--r--README.d/11-schedule-script.avifbin1847 -> 4113 bytes
-rw-r--r--README.md4
2 files changed, 2 insertions, 2 deletions
diff --git a/README.d/11-schedule-script.avif b/README.d/11-schedule-script.avif
index 27541b7..d6eb0f8 100644
--- a/README.d/11-schedule-script.avif
+++ b/README.d/11-schedule-script.avif
Binary files differ
diff --git a/README.md b/README.md
index 614095a..5109173 100644
--- a/README.md
+++ b/README.md
@@ -188,10 +188,10 @@ Scheduler and events
Most scripts are designed to run regularly from
[scheduler](https://wiki.mikrotik.com/wiki/Manual:System/Scheduler). We just
-added `check-routeros-update`, so let's run it every hour to make sure not to
+added `check-routeros-update`, so let's run it daily to make sure not to
miss an update.
- /system/scheduler/add name="check-routeros-update" interval=1h on-event="/system/script/run check-routeros-update;";
+ /system/scheduler/add name="check-routeros-update" interval=1d start-time=startup on-event="/system/script/run check-routeros-update;";
![screenshot: schedule script](README.d/11-schedule-script.avif)