Brian McDonald wrote:
What was it doing just before it starts doing this? For instance, can you
check your logs to isolate the file/attachment it was scanning? We had a
similar problem and I was able to identify a particular email attachment that
would send clamd (0.86.2) into just such a tailspin.
Hmm... It's hard to tell precisely (or even which of about 30) messages
might have been the last to hit the scanner. I'll ask our resident exim
expert if he can archive all attachments before they're sent to the
scanner, so we might have a shot at isolating the problem.
Kevin Way
InsideSystems
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
