Replies: 2 comments 1 reply
-
It's the other way around. The main time interval is for the main loop and in which all the sub sections are processed. However, it may be you have some sub sections that don't require that often processing (so they can be on a slower interval). So the interval of a sub section should equal the main interval, or be a multiply of that interval (or, when not a multiply it will be processed at the next main interval). Does that give the explanation you are looking for? |
Beta Was this translation helpful? Give feedback.
-
Unfortunately it still doesn't make sense, as much as I hate to say that out loud. I think I need a practical example. Let's look at "botupdater.ini" with the example data:
When I start botupdater.ini for the first time it turns on notifications, loads the database, fetches blacklist pairs, evaluates the details in [bu_default], decides whether to update the bots in [bu_default], then sends me a notification. Since the timeinterval is 24 hours, I'm assuming in one day it will do all of the above again. Is that correct? While botupdater.ini is running in the background there is a sub-section for [bu_default] bots. With the example data the same for the main and sub-section it is easy to understand that everything will update at the same time. I thought that having a sub-section interval for [bu_default] that was less than the main setting would cause the sub-section to update more often, but as I type this that wouldn't make sense because the main settings would be the same, as the main settings updates everything every 24 hours. Is that correct? If so, how does having a longer time interval for the sub-section work? My initial thoughts were that a longer interval for [bu_default] would be lost by the fact that the main script updates every 24 hours, wiping out the time interval for [bu_default] on it's refresh. I'm assuming that is wrong and when the main script updates it still stays open, tracking the longer interval for [bu_default] without wiping out the time tracking with the update. Is that correct? Do you have a practical example where someone would want to delay an update of a sub-section to a period longer than the main script updates? In my mind, if you are updating all of the data for the main script wouldn't you want to update your bots with that information as soon as it's available? Thank you for the help and for the prompt reply! I understand everything else in your scripts. |
Beta Was this translation helpful? Give feedback.
-
I'm just trying to understand better, but I can't find the answers I'm looking for in the documentation (I probably missed it). I understand that there is a Time Interval for most of the config files at the top and that is how often the script does it's next check. What I don't understand is the Time Intervals for the sub-sections. I would assume that the Time Intervals in the sub-sections must be the same as the Time Interval at the top of the config file, or shorter in duration. Despite that, if the script does another check based off of the master Time Interval at the top, what do the intervals in the sub-sections do? Will those parts of the script continue to run in the background on a second time interval before the interval at the top runs again? I just don't get it. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions