Trog wrote:
That's just it. I put a size limit on my mail system, BEFORE clamd has a chance to scan it,I know that the amount of memory used should be varied depending on system activity,
but when clamd uses 1 or 2 GB memory when it does nothing (well, it WAS very busy
earlier, but it's doing nothing now) is _weird_
If you're scanning multiple 1GB files concurrently, then your going to
use 1-2GB of memory.
so I know for a fact that no mail ever exceeds 50MB.
Perhaps MaxThreads 32 has something to do with the 3 GB memory usage ....
Okay. So lets say that clamd IS leak-free.It's up to your systems malloc/free implementation to decide when memory is released back to the system, not clams. So memory not going down during inactive periods is not "_weird_", it is entirely normal behaviour.
Lets say that the 3 GB is, in fact, memory that clamd used but system's "free" didn't return to the OS.
Now comes a question : what does clamd (the devel versions) do when it cannot allocate additional memory ?
I was under the impressions that old versions simply "returns an error and wait" instead of just died.
Which makes running daemontools alone insufficient.
If that were true, is there a plan to change that behaviour to "die/panic on memory errors"?
Is there any plan to implement some kind of built-in memory-limiter on clamd?
Regards,
Fajar
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
