On 16.09.2021 21:26, David Lang wrote:
On Thu, 16 Sep 2021, Mariusz Kruk via rsyslog wrote:
https://www.rsyslog.com/doc/v8-stable/configuration/modules/mmnormalize.html
"Note that mmnormalize should only be called once on each message.
Behaviour is undefined if multiple calls to mmnormalize happen for
the same message."
I called that out and it should have been removed from current
documentation.
OK. Good to know.
From my tests it turns out that even with direct queue the message
gets copied when entering a separate queue and thus the results are
not inherited on the ruleset (and queue) exit.
So it seems to be the mmnormalize that's causing the OP's variable to
be retained after the ruleset exit.
but if you don't specify any queue at all, then things inside a
ruleset will affect things outside the ruleset.
Sure. Then the flow inside a ruleset - which happens within the same
queue as the "outside", will affect the variables seen in the queue. I
use it heavily ;-)
But the OP asked about the direct queue and it seems that this queue
type is not "special" in anyway - it also creates a new scope.
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
