We started seeing this problem last night as well. Reading through the thread, it doesn't appear that ClamAV has fixed the signatures yet (as of 24257), or am I wrong?
-J On Fri, Jan 26, 2018 at 6:24 AM, Dianne Skoll <[email protected]> wrote: > On Fri, 26 Jan 2018 13:50:27 +0100 > Ralf Hildebrandt <[email protected]> wrote: > > > If I had to guess: they used the beta for testing, but the release > > versions (both 0.99.2 and 0.99.3!) fail to operate properly... > > No, I bet that's not what happened. A file descriptor leak doesn't show > up right away. They probably tested the signatures on a lightly-loaded > server and didn't notice any problems. > > ClamAV QA team: In future, please run new signatures against a clamd > process a few thousand times to check for possible resource leakage. > > Regards, > > Dianne. > > _______________________________________________ > clamav-users mailing list > [email protected] > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users > > > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml > _______________________________________________ clamav-users mailing list [email protected] http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
