Hi,
I found that this bug is due to the debian diff of the package syslog-ng-1.6.5-2.2
* Inspired by nsyslog, originally written by Darren Reed.
*
- * $Id: sources.c,v
1.37.4.4 2004/08/05 11:35:12 bazsi Exp $
+ * $Id: sources.c,v 1.37.4.2 2004/03/10 18:43:28 bazsi Exp $
*
***************************************************************
************/
@@ -121,13 +121,6 @@
full or we are a datagram receiver, when the
message is in
its own packet.
*/
- if (closure->dgram) {
- /* strip one trailing LF or NUL character
*/
- if (closure->pos > 0 &&
- (closure->buffer[closure->pos
- 1] == '\n' ||
- closure->buffer[closure->pos
- 1] == '\0'))
- closure->pos--;
- }
the debian patch removes the lines from source.c, that is not normal.
erasing this in the debian patch worked for me (no more NL/NUL char at the end of lines)
this can close #332554 for sarge too
version of the diff are clean since 1.6.8-1
Regards
PS : please excuse my poor english :)
--
Êtes-vous nostalgiques de cette époque où les hommes étaient des hommes, et écrivaient eux-mêmes leurs propres pilotes de périphériques?
