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