Bug#496254: Perl Syslog bug

[Gene Cash]

This also causes problems with syslog-ng. See message #64 by Balazs Scheidler in bug 356700 for a good explanation of the situation.

Here's possibly a better patch, which works with spamassassin and syslog-ng on my system. I'm using perl 5.10.0

--- Syslog.pm.orig	2009-04-16 10:24:55.000000000 -0400
+++ Syslog.pm	2009-04-16 10:25:47.000000000 -0400
@@ -405,7 +405,9 @@
 
 sub _syslog_send_console {
     my ($buf) = @_;
-    chop($buf); # delete the NUL from the end
+    # do not delete the NUL from the end, as it's the only thing to terminate
+    # messages when using unix-stream transport
+    # chop($buf);
     # The console print is a method which could block
     # so we do it in a child process and always return success
     # to the caller.

-- 
Gene Cash
Phone: 407-458-1596       Oracle Support Services (Orlando, FL USA)
A: Because it disturbs the logical flow of a message.
Q: Why is top posting a sloppy form of writing?