Hi Sam,
so what should I do now ?
As I can remember, I decreased that value to 20 or 10.
A long time ago I had 40 and during this time I had no problems with
crashing.
So what is to do, or better what is your suggestion.
Should I try now to trace the comm.flow or is that enough, what Jason Benguerel
wrote
that you will take care of that problem if you have to less processes and that
then it
could be possible for spammers to crash the MTA?
Many Thanks again for your help.
Cheers,
Maik
Sam Varshavchik wrote:
Jason Benguerel writes:
I had an old path in there, and when traffic hit 35 processes, it would
attempt to log a warning:
write(2, "WARN: 35 active connections.\n", 29) = -1 EPIPE (Broken pipe)
to the non existent (pipe?) and kill off the parent process.
This is a bit of a subtle misconfiguration, and only debugable via
strace
when you are actually hitting the ceiling of your MAXDAEMONS=40.
(Sam, don't
tear my head off, but would it make any sense to refuse to start if that
pipe is non-existent or not die if it can't be written to?)
Why would I want to tear your head off? This is certainly something
that needs to be addressed…
10 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Sometimes MTA cra...
