When ClamAV runs bytecode signatures, it uses a timer to limit the amount of processing.
Are you seeing it on a lot of files? If that is the case, the bytecode signature may require attention. You can try increasing the timeout limit. --bytecode-timeout for clamscan and BytecodeTimeout for clamd. Steve On Thu, Jul 20, 2017 at 9:47 AM, Mark Foley <mfo...@novatec-inc.com> wrote: > What is this? I just started happening. > > LibClamAV Warning: [Bytecode JIT]: Bytecode run timed out, timeout flag set > LibClamAV Warning: [Bytecode JIT]: recovered from error > LibClamAV Warning: [Bytecode JIT]: JITed code intercepted runtime error! > LibClamAV Warning: Bytcode 5 failed to run: Time limit reached > > Thanks, Mark > _______________________________________________ > 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
