I'm looking for a way to persist a :global variable so it survives a reboot.
Any ideas?
--jeroen
[Mikrotik follow-up needed] Any way to persist a :global variable so it survives reboot?
Last edited by jeroenp on Fri Oct 14, 2016 1:38 pm, edited 1 time in total.
Re: Any way to persist a :global variable so it survives reboot?
Try store them in "comment"
Re: Any way to persist a :global variable so it survives reboot?
What entity types would best be suited for such a comment?Try store them in "comment"
--jeroen
-
-
boen_robot
Forum Guru
- Posts: 2400
- Joined:
- Location: europe://Bulgaria/Plovdiv
Re: Any way to persist a :global variable so it survives reboot?
The "/system note" is a good place. It is displayed at the start of every terminal session, but beyond that, it doesn't ever "do" anything. Alternatively, you could create a custom disabled item at any menu, and use it as a comment. By virtue of being disabled, it won't do anything.
OR (my preferred approach), instead of doing that, you could write a startup script in "/system scheduler" that initializes the global variables to whatever values you need.
OR (my preferred approach), instead of doing that, you could write a startup script in "/system scheduler" that initializes the global variables to whatever values you need.
Re: Any way to persist a :global variable so it survives reboot?
Thanks. Since it's related to log buffers, I decided to put it in this entry (which I need to bail out on if it doesn't exist anyway):The "/system note" is a good place. It is displayed at the start of every terminal session, but beyond that, it doesn't ever "do" anything. Alternatively, you could create a custom disabled item at any menu, and use it as a comment. By virtue of being disabled, it won't do anything.
OR (my preferred approach), instead of doing that, you could write a startup script in "/system scheduler" that initializes the global variables to whatever values you need.
Code: Select all
:put [/system logging action print as-value where name=failedauth ]--jeroen
Re: Any way to persist a :global variable so it survives reboot?
Woot! You can set and retrieve the comment. But WinBox won't show it or allow you to change it.The not so cool (or - even though it's a bug - maybe cool), is that WinBox does not allow setting this comment.Code: Select all:put [/system logging action print as-value where name=failedauth ]
Pixie dust!
Code: Select all
/system logging action set failedauth comment=12
:put [/system logging action print as-value where name=failedauth]