Bug: nul chars at end of log lines
Hi, I reported this on 2004-11-24 as Debian bug against version 1.6.4, but I'm curious, whether problem is known on other platforms, too. (See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282782) A nul character at the end of an UDP transferred log message is included in the actual syslog file. In the terminal window the character is shown as ^@. Two problems: It looks ugly and it makes the file look "binary" to tools such as grep, which does not print lines anymore, but says "Binary file matches" :-( A test script to (< 15 lines of code) reproduce the behaviour can be downloaded from here: http://bugs.debian.org/cgi-bin/bugreport.cgi/logtest.py?bug=282782&msg=3&att... Don't forget to enable udp() as source, if you run the test. Cheers, WB
On Tue, 2005-04-19 at 12:13 +0200, W. Borgert wrote:
Hi,
I reported this on 2004-11-24 as Debian bug against version 1.6.4, but I'm curious, whether problem is known on other platforms, too. (See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282782)
A nul character at the end of an UDP transferred log message is included in the actual syslog file. In the terminal window the character is shown as ^@. Two problems: It looks ugly and it makes the file look "binary" to tools such as grep, which does not print lines anymore, but says "Binary file matches" :-(
A test script to (< 15 lines of code) reproduce the behaviour can be downloaded from here: http://bugs.debian.org/cgi-bin/bugreport.cgi/logtest.py?bug=282782&msg=3&att...
Don't forget to enable udp() as source, if you run the test.
This should have already been fixed in 1.6.5 -- Bazsi
participants (2)
-
Balazs Scheidler
-
W. Borgert