- This topic has 1 reply, 1 voice, and was last updated 20 years, 11 months ago by
.
-
Posts
-
I am seeing some interesting activity with the amavisd processes. All looks good until one of the processes decides to go hog wild with my RAM. I just killed a process that was using more than 550 megs of real memory. Needless to say this causes a variety of problems. Well mostly just SLOW delivery. And on a production day people don’t seem to like that?
I have not been able to determine what is the cause and was hoping someone had some ideas.
Anyone?
Josh
MacTroll wrote:
You do any custom edits to the files?
what files? postfix? amavisd?
the postfix conf file (main.cf) is modified.
I did make some changes to amavisd.conf but not until after all this went down. the only changes there I made:
$max_servers = 6; # number of pre-forked children (default 2)
$max_requests = 3; # retire a child after that many accepts (default 10)
- You must be logged in to reply to this topic.