I'm told that the current implementation for VirusEvent in clamd doesn't play 
well with OnAccess scanning due to the way clamd and OnAccess use threads and 
the way the current VirusEvent feature relies on forking.  VirusEvent was 
disabled when used with OnAccess until a better implementation can be 
implemented.

We have a bugzilla ticket here to track the issue: 
https://bugzilla.clamav.net/show_bug.cgi?id=12152.

Regards,
Micah

Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.


On Aug 3, 2018, at 10:38 PM, greengrasseyes 
<greengrasse...@protonmail.com<mailto:greengrasse...@protonmail.com>> wrote:

I am having a similar issue can anyone confirm or deny this is the
reason for issue:

https://bbs.archlinux.org/viewtopic.php?id=237489

_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
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
clamav-users@lists.clamav.net
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

Reply via email to