Description of problem: After one of the recent clamav updates I see that clamav-milter uses 100% cpu. strace shows a tight loop of: 22272 gettimeofday({1122994371, 371311}, NULL) = 0 22272 clock_gettime(CLOCK_REALTIME, {1122994371, 371339000}) = 0 22272 futex(0x805c958, FUTEX_WAKE, 1) = 0 22272 open("/var/lib/clamav", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 4 22272 fstat64(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 22272 fcntl64(4, F_SETFD, FD_CLOEXEC) = 0 22272 getdents64(4, /* 6 entries */, 4096) = 192 22272 stat64("/var/lib/clamav/daily.cvd", {st_mode=S_IFREG|0644, st_size=147768, ...}) = 0 22272 stat64("/var/lib/clamav/main.cvd", {st_mode=S_IFREG|0644, st_size=2337370, ...}) = 0 22272 getdents64(4, /* 0 entries */, 4096) = 0 22272 close(4) = 0 Version-Release number of selected component (if applicable): clamav-milter-0.86.2-4.fc3 How reproducible: everytime Additional Info: sysconfig/clamav-milter: CLAMAV_FLAGS='--max-children=2 -c /etc/clamd.d/milter.conf local:/var/run/clamav-milter/clamav.sock' CLAMAV_USER='clamilt'
Sorry, my bad. In attempting to fix the timeout issue with recent updates I foolishly set ReadTimeout to 0 in the config file.