problem with lines above 256 char. in log files

[Dominique Frise <dominique.frise (at) unil.ch>]

Hi Henrik,

Using 4.2.0 and all-in-one-patch.

Lines above 256 characters in log files are not parsed correctly and 
truncated.

Example
-----------------------
System logs at Tue Dec 2 22:08:23 CET 2008

red Critical entries in /var/log/messages
red CORE1 log_scsi_error, acsl 104 0 2 0, cmd 08 00 02 00 00 00 00 00 00 
00 00 00 target 01 host 00 driver 08 sense F0 00 20 00 01 80 00 16 00 00 
00 03 00 00 00 00 len 131072 ofs 0 type 1 in 1
----------------------

The complete line is:

"Dec  2 22:00:56 gollum kernel: FSNALIAS  Can't find this lun , failed 
command<6>IOCORE1 log_scsi_error, acsl 104 0 2 0, cmd 08 00 02 00 00 00 
00 00 00 00 00 00 target 01 host 00 driver 08 sense F0 00 20 00 01 80 00 
16 00 00 00 03 00 00 00 00 len 131072 ofs 0 type 1 in 1"


This line cannot be tested by hobbitd_client:

[bb (at) iris bin]$ ./hobbitd_client --test
Hostname (.=end, ?=dump, !=reload) []: gollum
Hosttype []: Linux
Test (cpu, mem, disk, proc, log, port): log
log filename: /var/log/messages
To read log data from a file, enter '@FILENAME' at the prompt
log line: Dec  2 22:00:56 gollum kernel: FSNALIAS  Can't find this lun , 
failed command<6>IOCORE1 log_scsi_error, acsl 104 0 2 0, cmd 08 00 02 00 
00 00 00 00 00 00 00 00 target 01 host 00 driver 08 sense F0 00 20 00 01 
80 00 16 00 00 00 03 00 00 00 00 len 131072 ofs ^C


Dominique
UNIL - University of Lausanne