<div dir="ltr"><div><div>hi,<br><br></div>I don't think that would help, sorry. Everyone is working on other stuff as it seems. Would you try to cook up a patch? I know it might intimidating at first, but you know it's all just code and computers :) not more complicated than a shell script. *<br><br></div>[*] ok, a bit more complicated, but everyone has to start somewhere :)<br><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">-- <br>Bazsi<br></div></div></div>
<br><div class="gmail_quote">On Tue, May 17, 2016 at 12:16 AM, Patrick Hemmer <span dir="ltr"><<a href="mailto:syslogng@stormcloud9.net" target="_blank">syslogng@stormcloud9.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Anybody? Should I open a new issue?<br>
<br>
-Patrick<div><div class="h5"><br>
<br>
<div>On 2016/3/28 12:01, Patrick Hemmer
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
I raised issue on an existing bug on the github tracker, but it
seems to have gone unnoticed, so I'm repeating it here to try and
get some attention on the issue.<br>
<br>
Using multi-line-mode without the multi-line-suffix option WILL
result in message loss.<br>
When syslog-ng is running in multi-line-mode, it buffers
multi-line messages until it sees the start of a new message. When
it sees the start of a new message, it flushes the buffered
message, and puts the first line of the new message in the buffer.
However if syslog-ng shuts down, or receives a SIGHUP (reload),
any lines currently buffered are discarded. Given that syslog-ng
can't stay running forever, and it will get shut down or SIGHUPd
eventually, using this feature will result in messages getting
lost.<br>
<br>
The message on the github issue where I brought this up is: <a href="https://github.com/balabit/syslog-ng/issues/140#issuecomment-197673887" target="_blank"></a><a href="https://github.com/balabit/syslog-ng/issues/140#issuecomment-197673887" target="_blank">https://github.com/balabit/syslog-ng/issues/140#issuecomment-197673887</a><br>
<br>
-Patrick<br>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>______________________________________________________________________________
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a>
</pre>
</blockquote>
<br>
</div>
<br>______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" rel="noreferrer" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" rel="noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br>
<br></blockquote></div><br></div>