David/James- Thanks for the input. The global directive is set as the first item after the module loading section, and the issue is still present. Any further suggestions?
-Logan On Wed, 20 Mar 2013, Boylan, James wrote: > You need to set that at the top of your config to have that actually take > effect. I ran into this same problem. For simplicity sake make it the first > line of your config. A more complete answer is that the config option only affects inputs after it in the config, so you could configure multiple inputs (on multiple ports) with different messages sizes if you wanted to by setting this to different values before the line that starts the listener. This is the way everything in the rsyslog config works, and most cases of 'why didn't this config option have the effect I expected' boil down to this type of problem. 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.
