On Fri, 17 Sep 2021, Mariusz Kruk via rsyslog wrote:
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.
the issue is that throughout the documentation, we say that not specifying a
queue is the same as specifying a queue type of direct. In this case, it's not.
so we can document this case where real-world behavior doesn't match the docs,
and add a large warning about it.
or
we can fix it to match the docs, and add a warning about the behavior change.
David Lang
_______________________________________________
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.
