David F. Skoll wrote:
> Ian Eiloart wrote:
> 
>>> Hold on here. Are you stating that you expect users to actually RTFM? I
>>> think you are expecting way too much.
> 
>> No, it's not. Not when the users are professional IT people.
> 
> :-)  I don't think we hang around the same "Professional IT people"
> 
>> The default configuration should suit personal installs, not corporate 
>> installs.
> 
> Why is that?  I bet most Clam users use it in a corporate or organizational
> setting (simply because most home users don't use *NIX).
> 
>> No upgrade should ever automatically change the current configuration file, 
>> except perhaps by adding documentation for new features. New features 
>> should work in a sensible way for personal installations without 
>> configuration.
> 
> No.  New features should require explicit enabling.  Personal installs
> can be served with the "config file template" idea where they say "give
> me every feature you've got!"
> 
> Regards,
> 
> David.

All of these problems are best discovered during the test stage in any event. 
Surely 
you don't drop a new untested build into production? I build the new releases 
in a 
dev environment, validate the config files to avoid surprises, look for new 
command 
line switches that are significant to my startup and run scripts. I then 
migrate it 
all to a test environment for full performance testing against sample data. 
Here 
freshclam is verified, as well. Finally it is put into the Cfengine data store 
and 
awaits the next Cfengine cycle at which time it is pushed out to production for 
all 
ClamAV class members in Cfengine. And then it is watched in those environments 
for 
surprises and if any are observed, Cfengine is used to retrograde the systems.

I have no need to trust the developers to do the right thing as a result. And I 
would 
do it this way even if I always found they did do the right thing because I'm 
finally 
responsible for installed software.

dp
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html

Reply via email to