Now after reading Rainer's comment - I realize what I posted above is probably impossible to do without breaking current output plugins API behavior.
On Thu, Apr 21, 2016 at 12:35 AM, Kane Kim <[email protected]> wrote: > Thanks for great explanation, David, that really helped me to understand > this part. What I'm suggesting is essentially this (and please correct me > if I'm telling obviously stupid things): > 1. Server tries to tell action1 to deliver messages (calling > EndTransaction) and has a loop here until it succeeds. > 2. Server tries to tell action2 to deliver messages (calling > EndTransaction) and has a loop here until it succeeds. > 3. Queue is locked/marked delivered/unlocked. > > As Rainer mentioned above that would lock only current queue where those > actions executed. > > > _______________________________________________ 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.
