apache22 and threads

Victor Sudakov sudakov at sibptus.tomsk.ru
Tue Sep 21 09:03:20 UTC 2010

Michael Powell wrote:
> > 
> > When building apache22 from ports, would you recommend to enable or to
> > disable threads support?
> > 
> > Even more confusing is the fact that for ports/www/apache22 the default
> > is: "Enable threads support in APR is off" (WITHOUT_THREADS=true)
> > 
> > while for ports/devel/apr1 the default is:
> > "Enable Threads in apr is on" (WITH_THREADS=true).
> > 
> > Thank you in advance for any input.
> > 
> > PS ports/devel/apr1 will also be used for the subversion client.
> > 
> I wouldn't mind someone with more apache22-fu to elaborate, correcting the 
> following if necessary.
> My thoughts are this matters depending upon which mpm you choose to build 
> into apache. The default is prefork, and it handles incoming requests by 
> spawning child processes. 

Do you mean to say "WITH_MPM=prefork" works exactly like apache13? 


> An additional consideration might be what kind of backend is used. For 
> example, since not all of PHP is known to be thread safe it is not 
> recommended for use with a threaded server and mod_php. The way to get 
> around this situation is to separate PHP from Apache with something like 
> mod_fcgid which runs PHP as a FastCGI. This way you can safely run a 
> threaded Apache with non-thread safe PHP. As far as which is the better 
> approach I still am not really sure. Each has its set of pros and cons.

 From what you have written it seems that prefork and no threads 
is the robustest, most reliable configuration (even if more resource

Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:sudakov at sibptus.tomsk.ru

More information about the freebsd-questions mailing list