David F. Skoll writes:
> But you are missing the point. The problem is not the configfiles. Anyone
> can easily edit a config file.
>
> The problem is that new behaviour suddenly appears when using an *old*
> configfile. It's the hard-coded defaults in the source that are the problem.
i'm probably going to get my tuchis flamed off here, but....
this is pre-version-1.0 software: it's a beta. who on earth upgrades
from one beta to another and uses the same configfile???
i'm not claiming that my upgrade procedure is ideal but at the very
least i do a line-by-line comparison of my existing configfile
with the template that comes with the newer version. i expect to have
to do that (or something like it) whenever fiddling with new versions
of stuff under active development.
when clam hits v1.0, i know my expectations will go up somewhat. but
until then, as long as the new template contains enough of an
explanation that i can tell "here be dragons", i'm happy.
> As I said before, as a general principle, new behaviour should not suddenly
> appear. It should have to be explicitly turned on.
post v1.0 i'd agree with you. this is beta software. expect surprises.
rp
rick pim [EMAIL PROTECTED]
information technology services (613) 533-2242
queen's university, kingston
-----------------------------------------------------------------------
"If it can't be done in VMS it isn't worth doing."
-- Harvey Brydon
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
