Steven Stern wrote:
Which is more efficient, running clamav-milter to call clamd (i.e., using --external) or letting clamav-milter do all the work? Does it make any difference? I'm running it on several MX servers, each handling about 3,000 messages/day. (Sendmail, clam, spamassassin on Fedora 5 or RHEL 4, 1GB memory, dual Xeon processors.)
I don't run clamav-milter so don't know if this is the case, but if each instance has to read and reload the databases for each scan then it is less costly to invoke clamd which has already read the databases and runs continuously. The milter I use (J-Chkmail) works this way. Clamd is started at bootup, and the milter drops any attachments into temporary storage, clamd is told where it is and to scan it. Seems very efficient.
dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
