-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for your explanation.
Best regards, Patrick Rainer Gerhards wrote: > Yes, that's right and that's the only solution for v3-stable. > > I haven't merged that change into the stable branch because, among all > of the changes done, this one is among those with the greatest potential > to break things. You do not want to have that in v3-stable (just to note > that backporting it is definitely not a good idea ;)). > > Rainer > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:rsyslog- >> [EMAIL PROTECTED] On Behalf Of Patrick Shen >> Sent: Wednesday, September 24, 2008 10:57 AM >> To: rsyslog-users >> Subject: [rsyslog] A question about message size >> > Hi Rainer, > > Now I am running latest V3 stable (3.18.4) on my company production > machine. We couldn't upgrade to >=3.21.4 to get the benefit of dynamic > setting MESSAGE size due to company policy. > > But we need 4K for message size not 2K by default. So I changed >> MAXLINE > definition in syslogd.h from 2048 to 4096. > > Is it correct? And do we have any other solutions with 3.18.4 ? > > Many thanks, > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog - -- Patrick Shen Operations Engineer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjaKPQACgkQkHhYtFevC+NsSACgiur1TmRgsFmE7qs8ff1c/xGF ifUAn2miAH8ILxk6KUiT2geoVRYXee/O =3pVu -----END PGP SIGNATURE----- _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
