[syslog-ng]Urgent: Mangled messages in pipe() destinations in version 1.5.19

[Carlos Inacio]

On Fri, Aug 02, 2002 at 05:26:25PM +0200, Andreas Schulze wrote:
> Hello Balazs,
> 
> in version 1.5.19 (and in other versions between >1.5.7 and <=1.5.19, too)
> we observing obscure message mangling in pipe() destinations.
> 
> Imagine the config below and the scenario:
> 	syslog-ng --write(2)--> pipe() --read(2)--> application
> 
> All four log paths below, writes lines to the pipe '/tmp/pipe'.
> With 1.5.7 we read from the pipe exactly that, what syslog-ng
> (using the config below) writes to it.
> 
> But with all newer versions (espec. 1.5.19) we read (with the same config):
> 
> message_1
> message_2
> messagmessage_4  !!!
> ...
> message_n
> 
> if we try to let syslog-ng write:
> 
> message_1
> message_2
> message_3
> message_4
> ...
> message_n
> 

Hi all,

We are seeing exactly the same behaviour Andreas described. Actually
it works fine until version 1.5.8, but if we use any version >1.5.8,
including patched 1.5.19 and 1.5.20, we get lots of mangled messages.
So it's not really the same problem that was fixed in 1.5.20.
Any ideas? We'd also love to use the latest version and not have to stick
to 1.5.8.

Thanks in advance,


Carlos Inacio.