trimhistory error

list Dirk Kastens
Thu, 24 Sep 2015 08:33:15 +0200
Message-Id: <user-9e3c140007ea@xymon.invalid>

Hi Japheth,

A quick fix is to re-split the lines on the datestamp so that the
history CGI can read through it.

I ran an "sed" script, yesterday, to clean up the logs. Now the display 
is ok. I will wait an see, if there will be new corrupted files after 
trimhistory is running.

Dirk