Hello, we thought a bit about this, and here's the solution that could satisfy everyone (TM):
for clamd we could provide different configfiles, depending on the needs the user can choose between 3 - or more templates, like: failsafe - most reliable standard - higher chance for a fp but also a better chance to catch bad stuff paranoid - detect everything ClamAV can detect - will raise a lot of fp for sure for clamscan we could provide this as switches The problem - you need to choose a template and copy it to the right location manually - new users need to read the manual to know about it - but that's not bad at all. So, what do you think - is this a solution that would work for the majority ? It would also be helpful - if this is a solution you could agree one - if you make suggestions what to include in the different files. -- Best regards, Christoph _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
