Greg Ames <[EMAIL PROTECTED]> writes:
> Jeff Trawick wrote:
> >
> > Greg Ames <[EMAIL PROTECTED]> writes:
>
> > > hmmm, seems like we have other cases like this already without order
> > > problems... <peeks at worker> Worker has pre-config logic to swap
> > > MaxClients and ThreadsPerChild if it doesn't like the order.
> >
> > I'll implement such since there is precedence (though I think it
> > wiser to make the admin re-order and avoid having to maintain such
> > code).
>
> yeah, that code isn't pretty. Could we do the HardServerLimit vs.
> MaxClient checking in a post-config hook? Seems like it would be much
> cleaner.
that's an idea... anything to avoid that tree twiddling!!!
but I think the problem there is that at initial startup
ap_log_error() calls (like those WARNING! messages for
inconsistencies) result in messages to the terminal, whereas we may
have lost that ability by the time we hit the post-config hook...
dunno... I'll try it...
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
