On Wed, 11 Apr 2001 [EMAIL PROTECTED] wrote:
> > What happens when you have incompatibility on a particular platform with
> > a MPM? It shouldn't just segfault, there should be a way to exit cleanly
> > explaining why this particular module or piece of code can not run with
> > the MPM used and the platform.
> If there is a compatability problem between a platform and an MPM, then we
> currently do not allow that MPM to be compiled on that platform without
> direct intervention from the person compiling the server. For example, on
> FreeBSD, we do not compile with threads unless the admin tells us we have
> to.
Right, I guess I didn't really phrase my question the right way.
How would you determine this incompatibility if you are a DSO module trying
run on Apache HTTP 2.0? Let say a module can only run on prefork, for
example.
> > The more accurate information you have in the noc the better. Why monitor
> > if you do not know what you are monitoring?
> The problem is that the MPM name is not accurate. We have a habit of
> changing names of things. The MPM properties are the best way to
> determine the behavior of the MPM IMNSHO.
Just because the MPM name isn't an accurate discription of what the properties
are of an MPM doesn't mean it could not useful to know what the MPM name is?
We should also keep in mind 3rd party MPMs such as the SGI STM MPM which
might accurately describe the MPM by it's name, but it is an identifier that
could point to the origin of the MPM.
--
Sander van Zoest [[EMAIL PROTECTED]]
Covalent Technologies, Inc. http://www.covalent.net/
(415) 536-5218 http://Sander.vanZoest.com/
