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
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 wher
If you got anything to say, please do.
But with this kind of awnsers i think nobody has anyting usefull about it..
Trog wrote:
On Fri, 2005-11-04 at 06:12 +0200, Shaun Bügler - Hetzner wrote:
Now, you are probably saying check
/usr/www/users/spacqre/cbn/search.php, but that not the issue. Ev
On Fri, 2005-11-04 at 06:12 +0200, Shaun Bügler - Hetzner wrote:
> Now, you are probably saying check
> /usr/www/users/spacqre/cbn/search.php, but that not the issue. Even if
> it has bad code in it, why does this affect clam?
GIGO
-trog
signature.asc
Description: This is a digitally signed
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 5
