I feel problem is not in config, but what clamd does when no config has
been set on that new function (tipical situation when you upgrade and
new features are available).
Even when example configs keep the state OFF, what happens when no
config has been set for that feature?
On minor releases I expect just to make a fast installation, not needing
to read all documentation and restuding the product.
On major releases, I find right to study all again.
So, I'd love:
* in minor releases (i.e. 0.92,0.93,0.94,etc) new features must be
OFF when they are not referred in any config. At the same way,
example config should keep them OFF.
* in major releases (i.e. 1.0,2.0) change what you want.
Tonino
Christoph Cordes ha scritto:
> 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.
>
>
--
------------------------------------------------------------
[EMAIL PROTECTED] Interazioni di Antonio Nati
http://www.interazioni.it [EMAIL PROTECTED]
------------------------------------------------------------
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
