Quoting Tomasz Kojm <[EMAIL PROTECTED]>:
> Oh, you're right - there was no chance to disable the timeout (however > clamav.conf states that 0 disables the limit). It's even better to use: > > if(timeout && ths[i].active) > > instead of > > if(timeout && (time(NULL) - ths[i].start > timeout)) > > I will fix it ASAP, thanks. > Your patch is incorrect. It will always be true for threads that are currently in use and they will instantly be killed. My patch fixes the 'no chance to disable the timeout', and by setting the timeout to 0 avoids the following 2 other bugs: 1. ths[i].start should be reset after each file is scanned 2. you can't mess with the ths[i] structure inside the threadwatcher thread without some locking -trog ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
