On Wed, 2013-03-27 at 13:24 +, Rodrian, Logan P (IS) wrote:
> David/James-
>
> Thanks for the input. The global directive is set as the first item after
> the module loading section
That's too later. When the modules load, they query the max size (at
least some do).
Rainer
> , and the issue
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 actuall
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
] On Behalf Of Rodrian, Logan P (IS)
Sent: Wednesday, March 20, 2013 1:27 PM
To: rsyslog@lists.adiscon.com
Subject: [rsyslog] Max Message Size
Hello-
I am using rsyslog across machines to send logs. I have the $MaxMessageSize
global directive set on both machines to 4096 (4k). Using wireshark
Hello-
I am using rsyslog across machines to send logs. I have the $MaxMessageSize
global directive set on both machines to 4096 (4k). Using wireshark between
the machines, I can see that the message text I am trying to send (2694) is
transmitted in its entirety. However, the syslog log file
5 matches
Mail list logo