2016-02-17 15:02 GMT+01:00 helices <[email protected]>: > 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. > > yup... messages are run one after another through the engine actions are executed in sequence when running without an action queue, the next action starts when the previous is finished if forwarding (or mysql) stalls, all other actions after it also stall
So in you setup you might not be interest in forwarding issues, but they still bite you ;) Rainer _______________________________________________ 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.
