Tim Rupp wrote:
Thomas Lamy wrote:
Tim Rupp wrote:
(From the qmailrocks website)
Now I'm going to throw in a small customization to Clam AV...
*mv /usr/bin/clamdscan /usr/bin/clamdscan.orig*
*ln -s /usr/bin/clamscan /usr/bin/clamdscan*
This sucks. With this setup, you're loading the virus-db for each and
every email. Set up clamd to listen on a TCP socket (dunno if qmail
runs in a chroot) and set the clamd user to somebody that is able to
read qmail's queue files. This is _way_ faster.
Sorry but I'm not a qmail guy. Else I'd re-write that howto ;-). And
up your softlimits, just to be sure (repeating a frequently given
answer).
Thomas
Hey dont shoot the messenger, I'm just going with what that tutorial
says and that's the same error I received when I followed that tutorial
and forgot the sym link. Yeah it may be horribly inefficient but I tried
to answer his question, pointing out what the potential cause of the
error may be. Let him go about changing stuff around after he figures
out what the error is. Bleh, sorry for the rant, I'll go back to work
now :-)
Tim
Sorry, I didn't want to be offending. Just wanted to point out a big
performance hole. And just in case he upgrades clamav one day, he'll get
into the same problems again, as the symlink will get overwritten. We
all know how long "temporary solutions" live, don't we?
Thomas
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
