Carlos E. R. wrote:
On 2014-05-07 16:55, Per Jessen wrote:
Carlos E. R. wrote:
But the issue, to me, is not really the huge memory, but that the child was not restarted after processing, if memory can not be freed.
Ah okay - I didn't realise that was the issue. That sounds like something to report to the spamassassin people.
Yes, memory is there to be used as needed, as long as it is released when not.
The max-conn-per-child switch handles that part, I think. Maybe that causes some performance decrease, spawning more often - but Linux is good at that.
And as you are not running a high-performance systems with thousands of users, it hardly matters anyway.
And if the openSUSE package is different than the upstream one (the obsolete man page indicates that), I can't report to them, but to openSUSE instead.
Nah, as long as the source version is the same, and the issue is reproducable, go ahead and talk to the SA guys. -- Per Jessen, Zürich (14.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org