----- Original Message -----
From: "Stephen Gran" <[EMAIL PROTECTED]>
To: <clamav-users@lists.clamav.net>
Sent: Friday, March 16, 2007 8:12 PM
Subject: Re: ClamAV not LOGGING viruses was [Clamav-users]
0.90.1notfindingviruses
On Fri, Mar 16, 2007 at 08:03:14PM -0400, John Fleming said:
That's not different though, from when it was logging the viruses to
clamav.log.
If you look at clamassassin, it does call clamscan, but again, it USED to
log virus names to clamav.log.
I have this idea that something in that paragraph is mistaken. clamscan
does not log to clamav.log, unless you ask it really nicely with some
extra command line arguments. This is possible, but the Occam's Razor
kind of guess is that something may have changed in clamassassin?
------------------------------------------------------------------------------
The mystery is that I was still using clamassassin 1.2.1 when I upgraded
clamav and the logging broke. During the thread I did upgrade clamassassin,
but the logging broke before that.
Let me clarify and summarize the order of events:
1. Using clamassassin 1.2.1 and clamav 0.88.x. Unsure if using clamscan or
clamdscan. Logging works
2. I upgraded clamav to 0.90.1 and viruses stopped being found at all, not
just not being logged. I restarted clamav-daemon several times and finally,
grasping for straws, uninstalled and reinstalled the debian stable clamav
package(s). At this point, viruses were being found again, but not being
logged.
3. Also, there was an error in freshclam about the configuration file not
being parsed. The suggested fix for this was:
CLAMSCANOPT="--no-summary --stdout --mbox"
Change this to:
CLAMSCANOPT="--no-summary --stdout"
(I don't see that this should affect logging, and it did fix the freshclam
error.)
4. Then I upgraded clamassassin 1.2.1 that I had manually edited to fix the
freshclam error, to 1.2.4 which was designed to work with clamav 0.90.1. At
first, I ran ./configure [alone] and was therefore using clamscan for sure,
as was reflected in the mail headers.
5. Finally, I reran ./configure --enable-clamdscan and logging returned to
normal.
I just don't understand the sequence. Upgrading clamav shouldn't have
affected anything about clamassassin.
Thanks - I think I've about beaten this to death! - John
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
