Eric Rostetter wrote: >> The principle of least surprise says ClamAV >> should reject that. By the same token, the principle of least surprise >> says that ClamAV should not break on previously-valid configuration files.
> But it is a big surprise when the action that old line was supposed to take > is no longer taken... Even worse if a new action is taken because a new > configuration line wasn't added when it needed to be. I suppose. But this is quite unlikely to happen. > Why do you think that software which is running and doing something other > than is expected/wanted is better than software which refuses to run when > there is a bad configuration given to it? I sure don't want my software > upgrade to change my policy without my knowing it... If you watch stderr and syslog, you will know it. -- David. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
