diff options
| author |  Christian Hesse <mail@eworm.de> | 2019-08-29 09:28:34 +0200 |
|---|---|---|
| committer | Christian Hesse <mail@eworm.de> | 2019-08-30 11:03:43 +0200 |
| commit | e479f3b01a0004c4488902f87658573ea9876af9 (patch) | |
| tree | 1ef6fcd06952b999ed5392d82a625920c36a43cf | |
| parent | 1ee3213e028e83564a0bae29294be41a9c3a54b2 (diff) | |
README: add valid script to scheduler
| -rw-r--r-- | README.md | 12 | ||||
| -rw-r--r-- | initial-commands | 4 |
2 files changed, 8 insertions, 8 deletions
@@ -96,8 +96,8 @@ And finally load configuration and functions and add the schedulers. [admin@MikroTik] > / system script run global-config [admin@MikroTik] > / system script run global-functions - [admin@MikroTik] > / system scheduler add name=global-config start-time=startup on-event=global-config - [admin@MikroTik] > / system scheduler add name=global-functions start-time=startup on-event=global-functions + [admin@MikroTik] > / system scheduler add name="global-config" start-time=startup on-event="/ system script run global-config;" + [admin@MikroTik] > / system scheduler add name="global-functions" start-time=startup on-event="/ system script run global-functions;" Updating scripts ---------------- @@ -112,7 +112,7 @@ Adding a script To add a script from the repository create a configuration item first, then update scripts to fetch the source. - [admin@MikroTik] > / system script add name=check-routeros-update + [admin@MikroTik] > / system script add name="check-routeros-update" [admin@MikroTik] > / system script run script-updates Scheduler and events @@ -123,16 +123,16 @@ Most scripts are designed to run regularly from added `check-routeros-update`, so let's run it every hour to make sure not to miss an update. - [admin@MikroTik] > / system scheduler add name=check-routeros-update interval=1h on-event=check-routeros-update + [admin@MikroTik] > / system scheduler add name="check-routeros-update" interval=1h on-event="/ system script run check-routeros-update;" Some events can run a script. If you want your DHCP hostnames to be available in DNS use `dhcp-to-dns` with the events from dhcp server. For a regular cleanup add a scheduler entry. - [admin@MikroTik] > / system script add name=dhcp-to-dns + [admin@MikroTik] > / system script add name="dhcp-to-dns" [admin@MikroTik] > / system script run script-updates [admin@MikroTik] > / ip dhcp-server set lease-script=dhcp-to-dns [ find ] - [admin@MikroTik] > / system scheduler add name=dhcp-to-dns interval=5m on-event=dhcp-to-dns + [admin@MikroTik] > / system scheduler add name="dhcp-to-dns" interval=5m on-event="/ system script run dhcp-to-dns;" There's much more to explore... Have fun! diff --git a/initial-commands b/initial-commands index cc15baf..c829875 100644 --- a/initial-commands +++ b/initial-commands @@ -23,7 +23,7 @@ run global-functions; } / system scheduler { - add name=global-config start-time=startup on-event=global-config; - add name=global-functions start-time=startup on-event=global-functions; + add name="global-config" start-time=startup on-event="/ system script run global-config;"; + add name="global-functions" start-time=startup on-event="/ system script run global-functions;"; } } |