Greg Ames <[EMAIL PROTECTED]> writes:
> > Hmmm... (2nd thoughts :) )
> >
> > mpm_default.h exists so people can edit default settings in one nice
> > place... it wasn't nice for me to move these things out of
> > mpm_defaults.h... I'll move them back in there... hopefully these
> > settings won't be abused by modules and instead modules will call
> > ap_mpm_query()
>
> I wouldn't move them back. If you keep them out of the header file,
> modules will have to use to use the MPM query functions, which is
> goodness. Once we decide how to configure the limits for worker and
> perchild, we can just use a subset of that stuff to set limits for the
> other MPMs.
>
> Prefork doesn't have the same potential memory consumption problem as
> worker, but it's still a pain to have to patch HARD_SERVER_LIMIT every
> time we put a new build on daedalus. I would think the same applies to
> Win32 and OS/2 with the current hard thread limits.
patch for daedalus^H^H^H^H^H^H^H^Hprefork on its way...
> Of course we don't want admins editing .c files as a rule. That would
> be a step backwards. But if our goal is to put these params in the
> config file, we can live with the limits in the MPM .c files for a day
> or two.
okay, let's defer any possible movement at least until we see what
MPMs folks want to make smarter...
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
