Quoting Colin Alston <[EMAIL PROTECTED]>:

> ClamAV has been continuously and repetitively adjusting configuration
> options in such a way that breaks anything which is automatically
> upgraded just stops working.

Well, maybe your "automatically upgrading" software needs improvment,
or just maybe you should follow standard best practices and not do
automatic upgrades on a critical/important production system?

> This is further aggravated by the fact that Exim does not know how to
> gracefully handle failures of clamav daemon.

Maybe you need to talk to exim about this then?

> Is there a reason people feel it necessary to fail startup on old
> configuration options?

Good question...

> Is there a reason it can't at least log
> deprecations ahead of time to allow people to transition smoothly
> between versions *without* their entire mail service grinding to a
> halt?

I doubt this is practical, and I doubt it would work well.  People who
do automatic upgrades and don't read the docs are not likely to read and
understand log messages either.

> Is there a reason these options have to change at all, or that
> the configuration parser can't know about old options for n versions
> and simply gracefully step over them?

You are using a pre-release fast changing piece of software.  Yes, it
will change.  If you don't like that, wait for version 1.0 before you
use it.

Yes, the parser could skip bad entries, but that would probably leave
users thinking that it was doing something that it wasn't, which would
be bad (and would generate much list traffic).

> It's a line-for-line configuration system, startup does not need to
> fail at all when options are unrecognised!

But if not, then the scanner may appear to work but be doing something
quite different than intended.  I mean, if it continued to run after
seeing unrecognized entries, which resulted in either a) all viruses
being passed through, or b) all files being marked as a virus whether
they are or not, that would be a bad thing.

> I think ClamAV should be mature enough now to start respecting the
> users it has and try to behave in a somewhat more stable way.

Let's see.  You want it to be mature, but it hasn't even had a 1.0 release?

You want it to respect the users by possible doing something other than
what they intended?

You think stability means doing something not intended?

> That is all, thank you for your time and the great work.

Hmmm...  Didn't think from the above you considered it such great work.
Glad to see you didn't toss the baby out with the bath water...

> --
> Colin Alston <[EMAIL PROTECTED]>

-- 
Eric Rostetter
The Department of Physics
The University of Texas at Austin

Go Longhorns!
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to