Matthew Callaway <[EMAIL PROTECTED]> wrote:
>I realize that the machine is old, and is running software that has
>updates, but the point is that a heavily loaded mail program shouldn't
>*kill* a machine.
When you say "kill", do you mean the system actually crashes, or just
slows to a crawl? If it crashes, that either a kernel bug or a
hardware error. If it slows dramatically, that's just what happens
when a system is severely overloaded.
>I would understand slow performance. How can you be
>sure that the hardware or the OS is buggy, and not qmail?
Assuming your system is really crashing, that has to be due to a
hardware error or kernel bug because there's nothing an application
like qmail can do to cause a crash. The worst that an application can
do is kill itself. Or does your OS have a crash() system call?
>I'm not that
>familiar with qmail. Could it be that qmail could be reconfigured to
>handle mail without bringing the system to its knees?
Sure. Set concurrencylocal to 1, concurrencyremote to 1, and run
tcpserver with "-c1".
-Dave
