On Wed, 26 Feb 2003, Rob Mueller wrote:
> [ Continued from an off mailing list conversation about killing Cyrus lmtpd
> processes when they go haywire, and cyrus process accounting ]
Actually, cyrus-devel would have probably been an even better place to put
this (and I'm cross-posting there).
>
From: "Rob Mueller" <[EMAIL PROTECTED]>
Date: Thu, 27 Feb 2003 08:22:09 +1100
[...]
In the case of cyrus, I think you can quite happily stick with the
multi-process model, I wasn't advocating moving to a threaded model. The
discussion started due to an issue with killing child proces
I will also add that on current *nix systems the advantages of threads
over processes is a lot less then it used to be. In my case we are running
apache2 on AIX and found no noticable difference between the two (so we
are useing processes for the stability reasons you note below)
David Lang
On T
> It is always a big pain to update code that was never written to be
> threaded, to be thread-safe. Apache2 has a problems with just about every
> third party module supported under Apache 1.3. I imagine that Cyrus would
> have all sorts of thread issues. There is no magic solution for that.
It is always a big pain to update code that was never written to be
threaded, to be thread-safe. Apache2 has a problems with just about every
third party module supported under Apache 1.3. I imagine that Cyrus would
have all sorts of thread issues. There is no magic solution for that.
Besi
as someone attempting to get apache 2 running (reliably) in a high volume
environment I can say the idea is interesting, but I definantly wouldn't
rush into useing it. if you have some time and want to get a start on
something that may (or may not) be worth doing in the long run you can
start on it
