Re: [clamav-users] signature memory use

doppelstern aren't used any more but I still mirror the blank files for a while so people's config don't break. Cheers, Steve Twitter: @sanesecurity On 28 December 2016 19:57:06 Alex wrote: Hi Steve, crdfam.clamav.hdb,pool memory used: 4.355 MB

Re: [clamav-users] signature memory use

Hi Steve, > crdfam.clamav.hdb,pool memory used: 4.355 MB > doppelstern-phishtank.ndb,pool memory used: 4.355 MB > doppelstern.hdb,pool memory used: 4.355 MB > doppelstern.ndb,pool memory used: 4.355 MB Can you explain what these are for? I don't see these on the signature description page:

Re: [clamav-users] signature memory use

Steve, > Time: 86.344 sec (1 m 26 s) That's why we should use clamdscan instead of clamscan. Clamscan reload all databases each time, this takes too much time. Btw, what was the CPU for this test ? -- Best regards, Arnaud Jacques SecuriteInfo.com Facebook :

Re: [clamav-users] signature memory use

> So all signatures should be running fine with 6Gb of RAM, right ? > Even our big signatures :) Summary test: Using clamscan only to scan test.eml (3,706 bytes) ClamAV Official sigs only (daily/main): pool memory used: 385.675 MB Official + *all* Sanesecurity/Distributed sigs pool memory

Re: [clamav-users] signature memory use

Thank you for your report Steve. > Official: Missing main.cvd :/ > Hope that helps see where some of the memory may be going, > sorry for not sorting... I'm under orders to go shopping ;) So all signatures should be running fine with 6Gb of RAM, right ? Even our big signatures :) -- Best

[clamav-users] signature memory use

As some people have reported memory issues... Quickly put these together based on scanning a small file and *only* loading *one* signature database at a time: Sanesecurity: badmacro.ndb,pool memory used: 5.132 MB blurl.ndb,pool memory used: 4.800 MB bofhland_cracked_URL.ndb,pool memory used: