On Tue, May 27, 2014 at 10:03 PM, Nick Syslog <[email protected]>wrote:
> I'm seeing cases where many of my large TCP events are now coming in > malformed after moving my MaxMessageSize parameters into the global() > configuration stanza and was digging through the net to find that people > were remediating the issue by placing MaxMessageSize prior to the module > load for IMTCP/IMUDP > > Is that still the case and should my global() definition reside above the > module definitions? > yes, there is a bug in imtcp. Note that imptcp and imudp work correctly. I'll look into fixing it. Thanks, 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. > _______________________________________________ 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.
