At 12:27 AM -0400 9/25/96, Evan Champion wrote:
>I just had a rather unfortunate incident where one of my list admins
>sent through something like 300 individual subscribe/unsubscribe
>messages as well as 4 or 5 postings to a 20000 user mailing list, all at
>once.
>
>Suffice it to say, my mail server didn't appreciate it at all :-)
>
>The basic problem, as I see it, is that Majordomo has no concept of
>system resources. I mean, it assumes everyone has enough CPU, memory
>and I/O capacity to handle any job, no matter how large.
I put the following lines in the very beginning of my majordomo.cf file a
few months ago, and they've worked very well. They basicly keep majordomo
(and anything else that executes the majordomo.cf file, like resend) from
executing if the load on the machine is over 8. You still get a perl
process starting up, but it will exit almost immediately with a "temporary
failure" indication to the mailer invoking it, which should cause the
mailer to simply queue the message and try again later. This works just
fine with Sendmail.
# Check the load; if it's too high, none of the rest of this matters...
$uptime = `/usr/bin/uptime`;
$uptime =~ s/.*:\s*//;
$uptime =~ s/,.*//;
if ($uptime >= 8.0) {
exit 75; # EX_TEMPFAIL
}
-Brent
----------------------+----------------------------+------------------------
Brent Chapman | Great Circle Associates | 1057 West Dana Street
Brent@GreatCircle.COM | http://www.greatcircle.com | Mountain View, CA 94041
----------------------+----------------------------+------------------------
Internet Tutorials from the Experts!
References:
|
|
