Bob Hutchinson wrote:
There is a thread going on in the logwatch ML, pertaining to a bug found in
the freshclam logging. It would appear to occur when syslog is used rather
than freshclam's own log in Fedora.
Looking at
clamav-devel/freshclam/manager.c
Line 67
logg("ClamAV update process started at %s", ctime(&currtime));
other uses of the logg function in manager.c *do* have a linefeed (\n)
Are you implying that there *should* be a linefeed? A post earlier this
morning seems to say that there *shouldnt* be any linefeeds. Im confused...
Hello,
First time posting to the list here. Perhaps this should have gone to the
developers list though - not sure.
Some of us over at the logwatch list have noticed that freshclam syslog
entries were not being detected by the logwatch filters. The cause of this
turned out to be that entries to syslog are being terminated with newlines,
which syslog happily turns into trailing spaces. For example (output using
vim's :set list command to end of line with a $):
Jan 15 05:01:34 glacier freshclam[30051]: Daemon started. $
Jan 15 05:01:34 glacier freshclam[30051]: ClamAV update process started at
Sun Jan 15 05:01:34 2006 $
Clamav is the only service that seems to include a newline in its syslog
entries. This should probably be stripped before being sent to syslog.
Thanks,
MrC
-Jim
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
