On Wed, 17 Feb 2016, helices wrote:
On Wed, Feb 17, 2016 at 1:43 AM, David Lang <[email protected]> wrote:
Also note that the queue you have setup only affects traffic destined to
the 172.31 destination, traffic to the 192.168 destination does not have an
action queue, so any backups or delays on that connection will delay all
messages, including ones written locally. This is one of the places where
the new style config makes it much clearer that the queue only applies to
the one action.
It's important to note that, in this thread, my ONLY concern is time to
write events to logfiles in /var/log/ - NOT any forwarding issues.
That's fine, but if forwarding or the database write block and they are working
from the main queue, all log processing is delayed.
think of it as there being one loop that runs through all the rules, if one rule
blocks, the loop cannot continue.
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.
