On Tue, May 02, 2006 at 05:40:56PM -0400, John Kelly wrote:
At startup, clamav-milter memory usage is approx. 11m resident and 30m
virtual. But when freshclam loads a new database, memory jumps to 20m
resident and 40m virtual.
I am seeing the same behaviour on clamd cross-compiled for
On Mon, May 01, 2006 at 04:49:27PM -0400, John Kelly wrote:
At startup, clamav-milter memory usage is approx. 11m resident and 30m
virtual. But when freshclam loads a new database, memory jumps to 20m
resident and 40m virtual.
The changelog for 0.86 says clamav-milter scans the old database
At startup, clamav-milter memory usage is approx. 11m resident and 30m
virtual. But when freshclam loads a new database, memory jumps to 20m
resident and 40m virtual.
I am seeing the same behaviour on clamd cross-compiled for ARM/Xscale. I
think this is caused by a great deal of memory
At startup, clamav-milter memory usage is approx. 11m resident and 30m
virtual. But when freshclam loads a new database, memory jumps to 20m
resident and 40m virtual.
The changelog for 0.86 says clamav-milter scans the old database while
waiting to become idle and reload the new database. But
