On Thursday November 15, 2007 at 06:18:40 (AM) Ian Eiloart wrote:
[ ... ]
Oh, but wait. What's going on here? You upgrade ClamAV and your
configuration changes? That shouldn't happen at all. Are you using an
installer tool that overwrites your deployed configuration? Surely not!
Excellent
On Nov 15, 2007 1:22 PM, David F. Skoll [EMAIL PROTECTED] wrote:
Ian Eiloart wrote:
Oh, but wait. What's going on here? You upgrade ClamAV and your
configuration changes? That shouldn't happen at all. Are you using an
installer tool that overwrites your deployed configuration? Surely not!
Ian Eiloart wrote:
Oh, but wait. What's going on here? You upgrade ClamAV and your
configuration changes? That shouldn't happen at all. Are you using an
installer tool that overwrites your deployed configuration? Surely not!
When we upgraded ClamAV, our configuration file stayed the same,
On Thu, Nov 15, 2007 at 01:28:39PM +0100, shuttlebox wrote:
On Nov 15, 2007 1:22 PM, David F. Skoll [EMAIL PROTECTED] wrote:
Oh, but wait. What's going on here? You upgrade ClamAV and your
configuration changes? That shouldn't happen at all. Are you using an
installer tool that
shuttlebox wrote:
We were not impressed with the decision taken by the Clam developers.
As a general principle of least surprise, new and experimental
behaviour should need to be enabled explicitly and not snuck in on
unsuspecting users.
Aren't these features only ever enabled if compiled
