Using clamdscan instead of clamscan to take advantage of multithreading?

[kieranjol]

In a similar vein to #65, clamscan tends to run quite slow in general. As a result, we've stoped running clamav as part of brunnhilde and run it seperately for timing and workflow reasons. I'm now realising that clamd+clamscan allows for the '-m' option to be triggered, which hugely speeds up performance, but adds complexity as it relies on the clamd.conf for settings and it requires the clamd daemon to be running. I've seen performance increases of about 6-8 times greater speed on mac and windows.

I think this is a significant change as launching the daemon is different on mac and windows.

[tw4l]

Interesting! I'm all for making changes to speed up virus scanning so long as the user configuration doesn't get too complicated. Would you have bandwidth to look into this a bit further?