Koozali.org: home of the SME Server

Contribs.org Forums => General Discussion => Topic started by: Knuddi on March 19, 2009, 10:29:40 AM

Title: ClamAV Statistics Contribution
Post by: Knuddi on March 19, 2009, 10:29:40 AM

As something new the ClamAV team is gathering statistic on what their engine finds around the world. In order to submit the statistic from a SME server a few additions to the freshclam.conf and clamd.conf files must be added (see http://www.clamav.net/support/faq-cctts/stats-howto). This should obviously be done via templates.

Create and open /etc/e-smith/templates/etc/freshclam.conf/SubmitDetectionStats and add the line:

SubmitDetectionStats /etc/clamd.conf

Create and open /etc/e-smith/templates/etc/clamd.conf/LogFile and add the line:

LogFile /var/log/clamav/clamdlog

Now we need to change the "LogTime" parameter to "yes". check first with - its properly "no"

Code: [Select]

db configuration getprop clamav LogTime
Now set it to "yes"

Code: [Select]

db configuration setprop clamav LogTime yes
Now we need to expand the templates:

Code: [Select]

expand-template /etc/clamd.conf

Code: [Select]

expand-template /etc/freshclam.conf
Now as the last thing activate it:

Code: [Select]

signal-event email-update
I actually suggest that this becomes the default configuration for SME servers going forward....

Enjoy,
Jesper

Title: Re: ClamAV Statistics Contribution
Post by: byte on March 19, 2009, 11:08:08 AM

Quote from: Knuddi on March 19, 2009, 10:29:40 AM

I actually suggest that this becomes the default configuration for SME servers going forward....

Jesper, have you raised a New Feature Request  (NFR) over on the bug tracker ? Thanks

Title: Re: ClamAV Statistics Contribution
Post by: Knuddi on March 19, 2009, 11:28:17 AM

Now it is: http://bugs.contribs.org/show_bug.cgi?id=5084

Title: Re: ClamAV Statistics Contribution
Post by: gzartman on March 27, 2009, 03:02:28 AM

Moved thread to General Discussion as it is more appropriate here.

Title: Re: ClamAV Statistics Contribution
Post by: holck on March 28, 2009, 12:04:09 AM

If you upgrade according to Jesper's description, I recommend that you also restart the freshclam service:

# sv restart freshclam

That service is not restarted as part of the signal-event email-update, so  the old version of freshclam will keep running, if you don't restart it in some other way.

Seems to work just fine here :-)