Well after a bit of research it seems that the clamscan process is using up all 1024 of the file descriptors allocated to it.
If I run clamscan for a while (at least half an hour) and then run something like lsof -p $(pidof clamscan) I get hundreds of the following entries:
clamscan 12016 root 9u REG 3,10 10354688 12 /tmp/tmpfAN4Rq7 (deleted)
Is it normal that clamscan has all these files open or should it be releasing them?
I am running version 0.60, should I download one of the recent snapshots and check whether the problem still occurs? Or should I just bump up the process file descriptor limit by running ulimit -n?
Cheers, Mike P.
You should definitely try one of the newer snapshots, or wait a few hours for Tomasz to put out the new release.
Thomas
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
