Ok, garbage in, garbage out.
So, how do I control the gigabytes of garbage that clamscan is spewing out?
Also, there is a directory rfc2397, and I would think that refers to the
rfc2397 - 'The data URL scheme' and that the problem would have to do
the code not following the rfc but no where
Shaun Bügler - Hetzner wanted us to know:
Any suggestions besides fix the php code ?
Run it manually and do an lsof on it to see what files it has open.
Run it manually and do an strace on it to see what the heck it's doing.
Run it manually and do whatever you gotta do to figure out where this
Hi guys,
Recently on a box we found that when clam was doing it nightly scan
(uses clamscan), it was creating huge temp files :
[EMAIL PROTECTED] clamav-768f23bf93fe051c]# ll
total 1001840
-rw---1 root root 512425984 Oct 26 07:43 comment.html
-rw---1 root root
