On Wed, 1 Jun 2005, Michael Parker wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David W Smith wrote:
So I reverted to SA 3.0.2 and the memory leak ceased rapidly plus
the load on the server normalized.
The SA 3.0.3 install had both the URIDNSBL and the SPF module
enabled (the enabling of the latter was new (on my server) to the
3.0.3 install and the memory leak continued with and without this
module enabled), as has the 3.0.2 install.
These two comments seem to contradict, did reverting to 3.0.2 help or
not? 3.0.3 removed a large memory issue with autowhitelist db files,
but otherwise 3.0.3 contained VERY SMALL changes.
--- Yes it did help, as my email said "I reverted to SA 3.0.2 and the
memory leak ceased rapidly". So I'm running SA 3.0.2 with the URIDNSBL and
the SPF modules enabled.
Also, how are you calling SA? Are you sure it is a memory leak and
not just a highwater mark? What sort of machine (memory wise) are you
running SA on and how many children are you starting? Is the machine
doing anything else?
--- Spamd is called via an '/etc/init.d' startup script. The server has
2Gb RAM. I'm not sure if I was seeing a memory leak or a highwater mark.
I just recall watching the 'free' column of the Swap output of 'watch -n
5 -d free' drop off to about 0.9 Gb in less than a minute before I
stopped SA. Usually free swap doesn't fall below about 1.9Gb on the
server. This server from inception has successfully run SA (started with
v3.0.1), Exim 4, Sophie 3.4rc2, Mailman 2.1.5, Squirrelmail 1.4.x, Apache
2.x, and NIS as the main applications.
Regards,
David Smith
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCndL4G4km+uS4gOIRAsjXAJsGyOJnwoyMTgt9SOZpDtDEbrylRACdF1LB
77mulc23GzAgHdsuhBhsrQM=
=NiQ8
-----END PGP SIGNATURE-----
