Edit the template file at /etc/clamav/clamd.conf.tmpl to disable DetectBrokenExecutables. Change it to no, I think, or comment out the line with a # since it is disabled by default. I don't remember the command to expand the template, but I think rebooting will cause it to expand to replace /etc/clamav/clamd.conf Don't edit /etc/clamav/clamd.conf directly because the next time the template is loaded, it will replace clamd.conf, but do look at /etc/clamav/clamd.conf to see if your changes show up... Hope this helps... From: Johann Scheiber [mailto:jo.schei...@sitco.at] Sent: Thursday, April 02, 2009 10:48 AM To: efw-user@lists.sourceforge.net Subject: [Efw-user] Total Crash Thank you for your reply, but I believe that the broken executable detection is definitely turned ON by default in EFW cause those entries can be found in the log on every installation from the beginning on "clamd[3821]: Detection of broken executables enabled" I have never changed anything except turning the ClamAV service on. The size of the hard drive is 20GB witch really should be enough. On another EFW I installed a 10GB large one and this EFW works fine since 6 month without causing any troubles. The usage of /dev/hda4 is 4% in this case, but the same services are running there with identical log configuration ! By the way, is there any possibility to clear the log manually?
__________ Information from ESET NOD32 Antivirus, version of virus signature database 3984 (20090402) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
------------------------------------------------------------------------------
_______________________________________________ Efw-user mailing list Efw-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/efw-user
