On Tue, 2002-02-05 at 13:16, Leonardo Cabral wrote: > Hi: > I'm quite new with courier, and I've a server running it since a few days > for testing. I another discussion list about other mail server, someone > wrote: > "No doubt! Courier has an interesting (and evidently fairly well-known) > little problem where you can "freak" it out and it'll spawn dozens of child
Dunno about "well known"... I've certainly never heard of such an issue
cropping up.
> processes and start "sending" itself so many messages that it'll bring your
> system logger to its knees by overloading it (sending it waaaaaaaay too much
> data waaaaay too fast for it to process or even queue to "catch up")
It's actually not that hard to choke Linux's standard syslog. Most of
the time it's configured to sync() the log files after every message,
which quickly dominates disk IO on *any* mail server software. It's not
a problem with Courier, you just need to set up your logger to not
sync() log files all the time.
> by an
> order of magnitude and ultimately panic the kernel.
Bahahahahaha! Anything that causes a kernel panic is a kernel bug. No
application bug should ever cause that to happen. Your poster is either
spreading FUD or has other problems to work out with his setup. (The
latter is possible, in accordance with Hanlon's Razor:
Never attribute to malice that which is adequately explained
by stupidity.)
signature.asc
Description: This is a digitally signed message part
