Hi Harald, we (and some other list members) observing the same problem. (see list thread "[syslog-ng]Urgent: Mangled messages in pipe() destinations in version 1.5.19" starting at 02/08) The last running version is 1.5.8. The bug is known to Bazsi. But unfortunately it isn't reproducable for him. Bazsi need more information! For us, its really hard to truss/strace our syslogd's, because they are heavy loaded. So, trussing will generate GB's of output and its hard to find the exact section, where the error occurs. Would be great, if you can strace your syslogd and send the output to Bazsi, to help him to fix this bug. Sounds that your syslogd isn't really high loaded. Thanks for your help! harald schmidt wrote:
Syslog-ng 1.5.21 still produces mangled messages into pipes! This happens ca. 10 times a day.
-- Best regards --Andreas Schulze [phone: +49.5246.80.1275, fax: +49.5246.80.2275] | I believe, it was Dennis Ritchie who said something like: | "C is rarely the best language for a given task, | but it's often the second-best". | The implication being that: "[...]" | | sh# cat>$$.c<<EOT | main(l,a,n,d)char**a;{for(d=atoi(a[1])/10*80-atoi(a[2])/5-596;n="@NK\ | ACLCCGZAAQBEAADAFaISADJABBA^SNLGAQABDAXIMBAACTBATAHDBANZcEMMCCCCAAhE\ | IJFAEAAABAfHJETBdFLDAANEfDNBPHdBcBBBEA_AL H E L L O, W O R L D! " | [l++-3];)for(;n-->64;)putchar(!d+++33^l&1);} | EOT | gcc -o$$ $$.c;clear;./$$ 52 8;rm -f $$*