On Nov 12, 2009, at 3:25 PM, Michael Scheidell wrote: > > observations include: > with build in CONTSCAN, amavisd loads the code once, and probaly caches > the unix socket. > with using clamdscan (tcp/remote) as the primary scanner, nothing is > cached, clamdscan needs to be called (the binary) for each message, > hence the question/request to support the TCP mode. > > if clamd supported both TCP and unix sockets on the same server, and you > had two servers, amavisd could use unix sockets for primary, and then > maybe tcp for backup scanner. > > has anyone else given this a try? > > your thoughts?
AFAIK clamd network TCP mode works only locally (so you would need NFS or something similar for checking files). That would also means that you would have NFS mounted amavis temp dir... I have tried this with version 0.94 but I haven't really checked later versions, so network-ed clamd would be nice thing... I have also ran into issues where clamd was failing and clamscan took too much cycles to process single email. What we do now, is check whether clamd is running and reverse check before upgrading clamd db. And so far, no problems with that. LP, Jernej ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
