Thanks for the info.
Do you know if this is specifically in regard to the worker MPM under
Apache and not the prefork MPM? Or does this not have anything to do
with threading?
[EMAIL PROTECTED] wrote:
On Fri, 14 Mar 2003, Michael Aaron wrote:
Sorry if this has been answered before but I can n
At 19:37 14.03.2003, Michael Aaron said:
[snip]
>Sorry if this has been answered before but I can not find it anywhere:
>
>Why does the PHP docs. state:
> "Do not use Apache 2.0 and PHP in a production environment neither on
>Unix nor on Windows. "
>
>What
On Fri, 14 Mar 2003, Michael Aaron wrote:
> Sorry if this has been answered before but I can not find it anywhere:
>
> Why does the PHP docs. state:
> "Do not use Apache 2.0 and PHP in a production environment neither on
> Unix nor on Windows. "
>
> What is the reason for this Warning?
The co
>
>Would I be able to install it along side 1.3 and run it on a separate
port?
I know some who installed two 1.3s in two different folders, run two
different daemons, in two different ports. I think it should work with 1.3
and 2.0 as well...
- E
>
>Cheers
>John Wards
>SportNetwork.net
>
>
>-
If you run Apache2 in prefork mode, it should mostly work with PHP. Don't
try to use one of the threaded mpms yet. The Apache 2 prefork mpm makes
it operate exactly like Apache 1.3 in the way it pre-forks processes and
handles one request per process.
-Rasmus
On Mon, 19 Aug 2002, John Wards wr
Wait until PHP 4.3.0 before considering Apache 2.0. Rasmus has indicated
they *may* play better together at that point. Currently, PHP 4.2.x with
Apache 2 is experimental and should not be used in a production environment.
We use it on our development server without trouble, but that server is
6 matches
Mail list logo
