httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@covalent.net
Subject Re: [PATCH] configuring APR threads fix
Date Tue, 31 Oct 2000 22:04:18 GMT

> You can pass additional command-line switches to the APR configure. This is
> not a problem to do (and I do it in Subversion). In fact, I made a patch a
> while back to apr_common.m4::RUN_SUBDIR_CONFIG_NOW() so that it can take
> these extra args.

I'll look into this later today.

> > That is why we have to check the cache.  I applied this patch, and it does
> > detect threads properly, but I ALWAYS configure with prefork, because it
> > is easier to debug the protocol code with that MPM, and APR all of a
> > sudden was being configured with threads, which breaks all sorts of
> > compile-time things.
> 
> As Ben points out, we must be able to have threads and prefork at the same
> time. It is entirely possible that a third-party module uses threads for its
> operation. Maybe by default, we won't enable them, but if --enable-threads
> is passed, then we should have threads enabled, despite the choice of MPM.
> 
> So... we should apply Joe's patch, but there are some other choices for how
> Apache calls the APR config.

We can't apply Joe's patch until the configuration is working
properly.  With this patch, things break with the prefork MPM.  Saying
that we are going to allow people to use threads with non-threaded MPMs
isn't as easy as you think, because there are other issues
involved.  Prefork allows people to use the old signals, but on Linux,
those signals won't work if we are threaded.

This all needs to be solved, but we can't apply the patch until they are.

Ryan

_______________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------


Mime
View raw message