:global persist do={

    :local varName $1
    :local varValue $2
    :local varID [/ip firewall layer7-protocol find name="$varName"]

    :if ([:typeof $varValue] = "nothing") do={
        :if ($varID != "") do={
            :set $varValue [/ip firewall layer7-protocol get $varID value-name=regexp]
        }
    } else={
        :if ($varID = "") do={
            /ip firewall layer7-protocol add name="$varName" regexp="$varValue"
        } else={
            /ip firewall layer7-protocol set $varID regexp="$varValue"
        }
    }

    return $varValue

}

• $persist name = Read persistent variable
• $persist name value = Write persistent variable
• :global name [$persist name] = Read persistent variable and write it to a global variable
• :global name [$persist name value] = Write data into a global variable and into a persistent variable at the same time

• The function uses layer7-protocols to store persistent data.
• All data read from persistent storage will be strings.
• The function always returns a value.

Did not see that before.
Why in the earth does not the RuterOS retains the global variable after reboot.
This should be a simple ting for MT to implement???

So MT consider this as a request.

Write variables in scheduler startup script is a better option than writing variables in l7 rules and other crazy stuff.

Write variables in scheduler startup script is a better option than writing variables in l7 rules and other crazy stuff.

• But... what with rapid power-off... data will be lost !
  L7 stay with latest one value ever reboot.
• But... scheduler will be create GLOBAL variable to other scripts can use it.
  Better is we stay with local and not use to many global.
  Each script can create local or global when he start, we not want a variable without latest value from before reboot.
• But... from scripting level we cannot edit the variable=value in some one line of scheduler on-event code!
  We cannot do export from only one scheduler to file,
  We cannot edit it via sed&awk - not work here... we not have proper workaround...

Write variables in scheduler startup script is a better option than writing variables in l7 rules and other crazy stuff.

Why in the earth does not the RuterOS retains the global variable after reboot.

• But... what with rapid power-off... data will be lost !
  L7 stay with latest one value ever reboot.

With L7 is the same as with scheduler configuration you have to write changes. If you do not write latest changes to scheduler or even your used L7 then of course nothing is saved.
Benefit of using startup scheduler is that you do not need to read and parse variables, they are just loaded at startup automatically.

• scheduler-env-startup - he create a global with default value
• scheduler-run-own-finall-app - this will be change our global
• scheduler-env-udpate - every x time it grab all global and replace data in scheduler-env-startup

Can you show any other scripting language or programming language where defined variables magically restores their values from previous script instance, without saving data to file, registry or database? If you want to save something handle it in your code.

Can you show any other scripting language or programming language where defined variables magically restores their values from previous script instance, without saving data to file, registry or database? If you want to save something handle it in your code.

See this post as an formal request for presistant variables.