It would be really handy to be able to get ClamSentinel to connect to a remote ClamAV TCP socket for the scanning instead of invoking ClamWin locally.
Potential use cases include:
1) Running a single dedicated machine on a fast network for AV scanning. Since AV is very CPU intensive, it would allow for better performance when there are many relatively light-weight client machines on the network that would be unbearably slow if they had to run all AV scanning locally.
2) Virtual machines could pass content to scan to the ClamAV running on the host. This would be beneficial because:
2.1) You wouldn't waste 100MB+ of RAM in each guest for ClamWin
2.2) The host ClamWin wouldn't suffer virtualization performance penalties (typically around 40% degradation compared to bare metal)
gordan_bobic ( gordan_bobic ) - 2012-07-06 04:36:20 PDT