On Fri, 31 May 2019, Peter Viskup via rsyslog wrote:
Date: Fri, 31 May 2019 09:03:20 +0200
From: Peter Viskup via rsyslog <[email protected]>
To: rsyslog-users <[email protected]>
Cc: Peter Viskup <[email protected]>
Subject: [rsyslog] call ruleset
From reading the call documentation [1] I understand the call ruleset can
be used to independent parallel message processing bypassing the standard
queue-lanes behavior [2].
Is this my assumption correct?
no, it just gives you a way to group rules and optionally have a queue for the
group of rules like you can have a queue for a single rule.
In the absense of additional queues and calling the same ruleset from multiple
places (in which case it could serialize processing, not cause more parallel
processing) it is functionally identical to pasting the rules from the ruleset
at the location of the call function.
David Lang
Want to come with configuration that will prevent unavailability of one
destination to block message processing of other actions.
then you need to add a new queue
Will the ruleset-linux use the default mainQ on input if not configured
with queue.* options?
it will continue to use the queue (and worker threads) that were in use at the
time of the call, these could be the main queue, or they could be another queue.
David Lang
_______________________________________________
rsyslog mailing list
http://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.
