That makes sense, and it'd be great if that's what it did, but it actually seems to just drop the rest of the message entirely.  The extra lines don't show up anywhere in the log file, with or without metadata.

Based on the search results I found on Google, I thought syslog-ng replaced newlines with spaces just like syslog.  So that's no longer the case?  I'd ask what version it was changed in, but I'm not seeing either behavior, so I doubt that's the issue.

Ian


On Wed, Dec 1, 2010 at 12:17 PM, Sandor Geller <Sandor.Geller@morganstanley.com> wrote:
Embedded newlines violate the traditional BSD syslog protocol so
syslog-ng treats newlines as terminators so the next line would be in
a new logmessage without timestamp, hostname, facility / priority,
etc.

On Wed, Dec 1, 2010 at 8:54 PM, Ian Lesperance <ianl@ezpublishing.com> wrote:
> When logging multiline messages (simple strings with in-line newlines) our
> logs only show the first line.  Everything after the first newline character
> is gone.
> We're on 3.0.5 and we don't seem to be using the no_multi_line option
> anywhere.  What else could explain this behavior?
>
> Ian
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.campin.net/syslog-ng/faq.html
>
>
>
______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.campin.net/syslog-ng/faq.html