It's not Linux but here is a piece of information that should help. NetWare is a thread only environment which means that we have been shipping and running all of the standard modules since day one with really no report of any threading related issues. I can't speak for any third party modules out there that may not be thread safe and I understand that Apache for NetWare has nowhere near the number of installations as Linux or others, but our standard modules seem to be doing well from a NetWare point of view. Even on multi-proc machines. Granted we don't normally stress test mod_example ;).
Brad >>> [EMAIL PROTECTED] Thursday, November 11, 2004 3:38:29 AM >>> On Sat, Nov 06, 2004 at 12:48:50AM -0800, Justin Erenkrantz wrote: > --On Saturday, November 6, 2004 8:28 AM +0000 [EMAIL PROTECTED] wrote: > > > @@ -125,6 +125,8 @@ > > +0: BrianP, Aaron (mutex contention is looking better with the > > latest code, let's continue tuning and testing), rederpj, > > jim > > -0: Lars > > + > > + pquerna: Do we want to change this for 2.2? > > Seems reasonable to do so. 2.0 was our first threaded release - making a > threaded MPM by default (if available) for 2.2 seems fine by me. -- justin I don't really agree with this. Many third-party modules still aren't thread-safe (and probably quite a few shipped in httpd too e.g. mod_example!). Making worker the default won't solve that, it'll just create a stream of "I upgraded to 2.2 and now everything segfaults" bug reports and people will stick with 1.3/2.0. 2.2 can be a compelling upgrade without making worker the default. joe
