httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <...@covalent.net>
Subject Re: [PATCH] mpm_query
Date Wed, 11 Apr 2001 17:39:49 GMT
On Wed, 11 Apr 2001, Sander van Zoest wrote:

> On Wed, 11 Apr 2001 rbb@covalent.net wrote:
>
> > I want to decouple the MPM query function from an actual name.  The goal
> > should be to report the properties of the MPM, not which exact MPM was
> > used.  Once that is done, the need for the string disappears.
>
> I would think you want to provide the actual name as well, on top of
> the properties. This probably could be listed just as APACHE_MPM_DIR which
> it could query the properties from the actual MPM via a common interface.
> Everything found in -V should be used for monitoring/logging.

That value is already compiled into the server.  But there is currently no
way to query it.

> 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.

> 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.

Ryan

_______________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------


Mime
View raw message