Effectiveness of a script policy? Scheduler policy?
Posted: Tue Mar 20, 2012 2:08 pm
Hi,
I just wrote a short script to refresh the SMTP server IP address from its FQDN (since routerOS won't access anything except an @IP...), and see something strange: script policy is "read,test", but it still can change email server setup when run directly from CLI...
Why is this script behaving like it has "write" policy applied? Are script policies even effective?
Now, another question: what does a scheduler policy mean? Why would it be different from the script it runs?
I just wrote a short script to refresh the SMTP server IP address from its FQDN (since routerOS won't access anything except an @IP...), and see something strange: script policy is "read,test", but it still can change email server setup when run directly from CLI...
Code: Select all
name="script-SMTPrefresh" owner="elgo" policy=read,test last-started=mar/20/2012 12:56:12 run-count=4
source=
# refresh SMTP server address used for email notifications
# because email parameter can't be a FQDN but only an IP address
:local smtp [:resolve ("smtp.gmail.com")]
/tool e-mail set address=$smtp
:log info ("SMTP server updated: ".$smtp)
Why is this script behaving like it has "write" policy applied? Are script policies even effective?
Now, another question: what does a scheduler policy mean? Why would it be different from the script it runs?