Mailscanner warnings

[Glenn Steen]

On 15/02/2008, AlxFrag <alxfrag at gmail.com> wrote:
>
(snip)
>
>  It says:
>
>  clamav          /usr/lib/MailScanner/clamav-wrapper
> /usr/local
>  clamd           /bin/false
> /usr/local
>
>
>
>  and , in /usr/lib/MailScanner/clamav-wrapper i have:
>
>  ClamScan=$1/bin/clamdscan
>
>
That is _not_ the recommended and supported way of using clamd in
MailScanner. You will pay an unnecessary fork/exec penalty for this,
compared to the very nice direct call thing Rick Cooper implemented.
The reason to not use clamavmodule (mainly, apart from some possible
build issues) and use Rick's clamd thing instead is that the
individual MS child memory footprint is decreased (using clamd)...
Since clamavmodule will have to load the signatures into every child.

Please undo those mods and look at implementing clamd the right way instead;-).

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se