John,
The work-around that I've patched together is a total hack, but it
works. Here's the script that I run every 5 minutes from cron.
...
echo Running amavisd-nanny for 3 minutes to clean up stuck processes.
/usr/local/bin/limit 180 /usr/sbin/amavisd-nanny 1/dev/null 2/dev/null
The
On Thu, 6 Mar 2008, Mark Martinec wrote:
It basically waits for X seconds (in this case 180) and if the program
is still running after X seconds, it kills it. This allows me to run
amavisd-nanny for 3 minutes without direct user intervention.
Btw, the amavisd-new-2.6.0 will provide an option
Greetings,
I sent the following email a week ago, and I have not seen any
responses to it. I'm going to assume the message never hit the list
(even though I received it back from the list.)
Does anyone have any information on this?
Original Email Below
All,
Since
All,
Since migrating to Postfix+Amavisd-new+SpamAssassin+ClamAV a few months
back, I've had some issues with amavisd-new going out of control and
consuming a massive amount of CPU time. The load on my box is normally
less than 0.8, but when amavisd-new goes crazy, the load will climb to
over 7
