Aaron Bannert <[EMAIL PROTECTED]> writes:
> The hard part about this (at least for me) is the multitude of variables
> that go in to deciding the implementation of the accept() mutex. Is there
> a way I can find out (at runtime) what implementation is being used?
Put "AcceptMutex foo" in your apache configuration file.
Either "foo" is the mechanism or Apache will fail to initialize.
(If you really do put "AcceptMutex foo" literally in your config file,
the resulting error message will display suitable replacements for
"foo" on your system :) )
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
- OSDLab projectL Accept() locking on large (6+ CPU) b... Dirk-Willem van Gulik
- Re: OSDLab projectL Accept() locking on large (... Aaron Bannert
- Re: OSDLab projectL Accept() locking on lar... Brian Pane
- Re: OSDLab projectL Accept() locking on... Aaron Bannert
- Re: OSDLab projectL Accept() lockin... Brian Pane
- Re: OSDLab projectL Accept() lockin... Bill Stoddard
- Re: OSDLab projectL Accept() lockin... Jeff Trawick
- Re: OSDLab projectL Accept() locking on... Justin Erenkrantz
- Re: OSDLab projectL Accept() lockin... Aaron Bannert
- Re: OSDLab projectL Accept() locking on large (... Bill Stoddard
- Re: OSDLab projectL Accept() locking on lar... Dirk-Willem van Gulik
- Re: OSDLab projectL Accept() locking on... Ian Holsman
- Re: OSDLab projectL Accept() lockin... Dirk-Willem van Gulik
- Re: OSDLab projectL Accept() locking on large (... Ben Hyde
