[quote user="Heini_net"]
but shoutd mercury use an external daemon or its better if mercury run clamwv automaticially ?
[/quote]I'd say it doesn't make much of a difference. ClamWall just runs ClamD/FreshClam with the --config-file= parameter, which points to the config file you have configured in ClamWall. This allows to run ClamD/FreshClam from a location which is different from c:\clamav but otherwise it's pretty much the same.
Best regards,
Nico
[quote user="Heini_net"]<P> but shoutd mercury use an external daemon or its better if mercury run clamwv automaticially ?</P>[/quote]
I'd say it doesn't make much of a difference. ClamWall just runs ClamD/FreshClam with the --config-file= parameter, which points to the config file you have configured in ClamWall. This allows to run ClamD/FreshClam from a location which is different from c:\clamav but otherwise it's pretty much the same.
Best regards,
Nico