In message <9203dabf-59fb-4462-9ca5-7d90fb265...@edisoninfo.com> Gary MacKay <g...@edisoninfo.com> was claimed to have wrote:
> >On Apr 16, 2010, at 2:56 PM, Eric Rostetter wrote: > >> Quoting Gary MacKay <g...@edisoninfo.com>: >> >>> OK, who's the mental midget that decided to just up >>> and kill all installations of clamav ??? >> >> No one. Only very old installs, not all installs. >> >So who made who god to decide which servers get shutdown? Will the server not boot? >>> OK, so the version is not updated and it is probably not catching all >>> the viri that is should. SO WHAT!!!! >> >> So why run it at all? And why stop the rest of us from being able to >> catch all the viri we should be able to, and want to? >> >Nobody is stopping you from doing whatever you want to YOUR servers. Correct. You picked what should happen in the "SO WHAT!!!!" case described as above. Personally, my servers keep delivering mail in the event of a ClamD failure. I run multiple scanning engines and so I am tolerant of a single one failing. Why did you configure your server to "shutdown" if ClamD fails if what you actually wanted was mail to still flow unscanned? Given that Clam announced upcoming failures for out of date versions, and given your configuration choice, what did you expect would happen? _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
