-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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,
- --
Patrick Shen
Operations Engineer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkjaAL4ACgkQkHhYtFevC+PhBgCfVnsQU4Zcn9rVgWZIpS5WXqWz
YxMAn3GWCZ2bPvJFthSCb2HECCfIkF7Y
=Rza/
-----END PGP SIGNATURE-----
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
Hash: SHA1
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,
- --
Patrick Shen
Operations Engineer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkjaAL4ACgkQkHhYtFevC+PhBgCfVnsQU4Zcn9rVgWZIpS5WXqWz
YxMAn3GWCZ2bPvJFthSCb2HECCfIkF7Y
=Rza/
-----END PGP SIGNATURE-----
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog