You could also run a second copy of syslog-ng on the host that has a shorter message. Use that instance to forward the logs to the other destination. This avoids you having to writ your own program :-) On 02/19/2014 02:17 AM, David Schweikert wrote:
Hi Sandor,
Thanks for the quick reply and a proposed workaround.
On Wed, Feb 19, 2014 at 09:02:23 +0100, Sandor Geller wrote:
Truncating log messages? Sorry, but this just doesn't sound right when it comes to syslog-ng itself.
Why does it make sense in a source context but not in a destination context?
You could argue that it makes even more sense in a destination context, because it allows to deal with legacy systems, whereas syslog-ng doesn't need any size limitations.
Cheers David ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
-- Evan Rempel erempel@uvic.ca Senior Systems Administrator 250.721.7691 Data Centre Services, University Systems, University of Victoria