Re: recommanded configure for 2.0.24 ?
Justin Erenkrantz wrote: On Sun, Aug 26, 2001 at 02:19:54AM +0200, Gomez Henri wrote: Yes, on Linux prefork is selected by default. threaded seems to works fine, but perchild is no more useable since mod_ssl failed to build. Yeah, but there are outstanding issues with threaded MPM that make me leery of recommending threaded for end-users until we resolve them. Henry, Last time I checked, worker had a problem handling more than one concurrent connection per process. So I would advise you to test worker vs. threaded before you make a decision. Greg
Re: recommanded configure for 2.0.24 ?
Greg Ames [EMAIL PROTECTED] writes: Last time I checked, worker had a problem handling more than one concurrent connection per process. So I would advise you to test worker vs. threaded before you make a decision. I just tried worker with Aaron Bannert's fixes applied. It is finally working reasonably for me with many concurrent connections. -- Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...
Re: recommanded configure for 2.0.24 ?
On Sun, Aug 26, 2001 at 02:06:53AM +0200, Gomez Henri wrote: May be the following is more recommanded ? ./configure \ --with-mpm=threaded \ --enable-so \ --enable-module=all \ --enable-mods-shared=all \ --enable-so \ --enable-ssl --with-ssl=/usr/include/ Yes, I'd recommend this one as it is much cleaner. =-) Maybe --enable-mods-shared=most as it will disable modules that aren't supported on your platform (all will stop if it finds a module that can't be built). I wouldn't specify the --with-mpm as this allows us to specify the MPM. Our default is prefork for a good reason. =-) -- justin Yes, on Linux prefork is selected by default. threaded seems to works fine, but perchild is no more useable since mod_ssl failed to build. Using prefork mode on Linux make Apache 2.0 equivalent to Apache 1.3 ? No more threads in that case ? I've got a question for you gurus, I'm working on mod_jk, tomcat connector, and I must make some task ONLY one time, regardless of MPM used (threading, forked, mixed). What strategy could I use ?
Re: recommanded configure for 2.0.24 ?
On Sun, Aug 26, 2001 at 02:19:54AM +0200, Gomez Henri wrote: Yes, on Linux prefork is selected by default. threaded seems to works fine, but perchild is no more useable since mod_ssl failed to build. Yeah, but there are outstanding issues with threaded MPM that make me leery of recommending threaded for end-users until we resolve them. Threaded MPM works, but there are some issues that I don't think can be resolved in the current code. The long-term alternative is the worker MPM - Aaron just submitted (and rbb committed) a patch that should go a long way to get worker MPM up. I haven't had a chance to test it yet, but I will try to do so soon. If you want to try out threads, you may want to try the worker MPM. (God, these MPM names are wretched.) Using prefork mode on Linux make Apache 2.0 equivalent to Apache 1.3 ? No more threads in that case ? Yeah. On Linux, threads are equivalent to processes anyway, so it isn't a big deal. Solaris is a different story though. I've got a question for you gurus, I'm working on mod_jk, tomcat connector, and I must make some task ONLY one time, regardless of MPM used (threading, forked, mixed). The post_config hook is probably your best bet. -- justin
recommanded configure for 2.0.24 ?
Also what's the recommanded ./configure params on Linux boxes ? I'm using the following which may be a little longer ./configure \ --with-mpm=threaded \ --enable-so \ --enable-env=shared \ --enable-setenvif=shared \ --enable-unique_id=shared \ --enable-mime=shared \ --enable-mime_magic=shared \ --enable-negotiation=shared \ --enable-alias=shared \ --enable-rewrite=shared \ --enable-userdir=shared \ --enable-speling=shared \ --enable-dir=shared \ --enable-autoindex=shared \ --enable-access=shared \ --enable-auth=shared \ --enable-auth_anon=shared \ --enable-auth_db=shared \ --enable-auth_dbm=shared \ --enable-auth_digest=shared \ --enable-headers=shared \ --enable-cern_meta=shared \ --enable-expires=shared \ --enable-asis=shared \ --enable-include=shared \ --enable-cgi=shared \ --enable-cgid=shared \ --enable-actions=shared \ --enable-status=shared \ --enable-info=shared \ --enable-log_config=shared \ --enable-usertrack=shared \ --enable-imap=shared \ --enable-mmap_static=shared \ --enable-dav=shared \ --enable-dav-fs=shared \ --enable-vhost-alias=shared \ --enable-echo=shared \ --enable-cache=shared \ --enable-suexec=shared \ --enable-ssl=shared \ --with-ssl=/usr May be the following is more recommanded ? ./configure \ --with-mpm=threaded \ --enable-so \ --enable-module=all \ --enable-mods-shared=all \ --enable-so \ --enable-ssl --with-ssl=/usr/include/ Thanks for your advice, AP 2.0 gurus
