It has nothing to do with the logInfo, it has everything to do with actually running a rule in the rules file itself. The call to logInfo is just there for me to visually see that it ran. The call to logInfo could be removed and do nothing but run the rule, and it would still serve its purpose of having a rule run right away.
Having a rule run right away seams to remove the delay I have been getting for any of the other rules that have yet to run in the same rules file.
I’m a bit confused right now. naming your rule after the file the rule is in (or another file with another rule) doesn’t have any effect at all. The rule name is just that - a name.
or do I miss the April’s fool here?
I don’t even know what you are talking about. I never said anything about a rules file name. The only thing that is important for this, is that a “System started” rule is added to every rules file, if it does not already contain one. Nothing more, nothing less.
Now I understand - and you’re absolutely right. This one did the trick and I don’t have to worry about delays anymore - of course the only downside is, your system takes a wee bit longer to start but then you’re done forever and rules get processed even faster, yes.