Re: [PHP] PHP and Apache 2
On Sun, 8 Aug 2004 16:20:55 +0300, Rosen <[EMAIL PROTECTED]> wrote: Hi, What is the reason, thath in the installation manual of PHP writes: "WARNING: Do not use Apache 2.0 and PHP in a production environment neither on Unix nor on Windows. " Thanks, Rosen http://www.zend.com/lists/php-dev/200406/msg00291.html -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP and Apache 2
Hi, What is the reason, thath in the installation manual of PHP writes: "WARNING: Do not use Apache 2.0 and PHP in a production environment neither on Unix nor on Windows. " Thanks, Rosen -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] PHP and Apache 2
On 13 Mar 2004 Rasmus Lerdorf wrote: > I think that is pretty clear. It says that it works but we do not > consider it production quality. OK, thanks. That is what I thought it meant but I wanted to be sure. > As for whether your particular install will work? I have no idea. Maybe, > maybe not. And if weird things happen chances are we won't be able to > help you fix it. That's the essence of our reccomendation to stick with > the Apache1 codebase we know well until such a time that Apache2 actually > delivers substantial enough features to warrant the effort it is going to > take to hammer it into a production-quality environment. Thanks. I wasn't asking if it would work, just what the recommendations were. That's very clear. -- Tom -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] PHP and Apache 2
On Sat, 13 Mar 2004 [EMAIL PROTECTED] wrote: > > So the current situation is that Apache2-prefork+PHP is a decent solution > > but it hasn't been tested a whole lot. > > I am currently moving my app to an Apache 2 server. I did not build > the server (not my area of expertise) and don't know how how it was > built, but I can talk to the folks who did it and find out. It was > their choice to go to Apache 2, but I still have time to get them to go > back if need be. I'd like to understand the recommendations more > clearly. > > Are there configurations of Apache 2 that are OK with PHP? The above > suggests prefork hasn't been tested but the remainder of your message > suggests multithreading (which is different from prefork as I read the > Apache docs -- right?) is even more problematic. It sounds like this > is what's behind the recommendation at > http://us2.php.net/install.apache2 which says "Do not use Apache 2.0 > and PHP in a production environment neither on Unix nor on Windows." > But the same page says "The following versions of PHP are known to work > with the most recent version of Apache 2.0:", so I'm not quite clear on > what's being recommended. I think that is pretty clear. It says that it works but we do not consider it production quality. As for whether your particular install will work? I have no idea. Maybe, maybe not. And if weird things happen chances are we won't be able to help you fix it. That's the essence of our reccomendation to stick with the Apache1 codebase we know well until such a time that Apache2 actually delivers substantial enough features to warrant the effort it is going to take to hammer it into a production-quality environment. -Rasmus -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP and Apache 2
> So the current situation is that Apache2-prefork+PHP is a decent solution > but it hasn't been tested a whole lot. I am currently moving my app to an Apache 2 server. I did not build the server (not my area of expertise) and don't know how how it was built, but I can talk to the folks who did it and find out. It was their choice to go to Apache 2, but I still have time to get them to go back if need be. I'd like to understand the recommendations more clearly. Are there configurations of Apache 2 that are OK with PHP? The above suggests prefork hasn't been tested but the remainder of your message suggests multithreading (which is different from prefork as I read the Apache docs -- right?) is even more problematic. It sounds like this is what's behind the recommendation at http://us2.php.net/install.apache2 which says "Do not use Apache 2.0 and PHP in a production environment neither on Unix nor on Windows." But the same page says "The following versions of PHP are known to work with the most recent version of Apache 2.0:", so I'm not quite clear on what's being recommended. FWIW httpd-l on the new server shows: Compiled in modules: core.c mod_access.c mod_auth.c mod_include.c mod_log_config.c mod_env.c mod_setenvif.c mod_ssl.c prefork.c http_core.c mod_mime.c mod_status.c mod_autoindex.c mod_asis.c mod_suexec.c mod_cgi.c mod_negotiation.c mod_dir.c mod_imap.c mod_actions.c mod_userdir.c mod_alias.c mod_so.c Thanks for any comments. -- Tom -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] PHP and Apache 2 (Was: Ver 5.0 Questions ...)
Chris Shiflett wrote: > So, I'm not sure what documentation you're referring to exactly, nor > am I sure that there would be a lot of support in updating it. This one: -8<. Warning Do not use Apache 2.0 and PHP in a production environment neither on Unix nor on Windows. -8<. You find it here: http://www.php.net/manual/en/install.apache2.php /Thomas -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] PHP and Apache 2 (Was: Ver 5.0 Questions ...)
--- Thomas Svenson <[EMAIL PROTECTED]> wrote: > I am using the pre-forked model in Apache2 yes. So far I haven't > noticed any problems with PHP(4/5beta). > > If the problems with PHP is with the non pre-forked models, then its > time to update the recommendation to not run PHP on Apache2. Instead > it should explain why it doesn't work and that if pre-forked is used > there are no problems. This topic was brought up at ApacheCon. The mod_perl developers have the same potential problems with threading - even when the core is thread-safe, many extensions are not. If you are running in pre-fork mode, there are really no conflicts or problems with running PHP on Apache 2. However, Rasmus still feels strongly about using Apache 1.3 until 2 has been around for a long time (1.3's stability is hard to match), unless you have a compelling reason to upgrade. So, I'm not sure what documentation you're referring to exactly, nor am I sure that there would be a lot of support in updating it. Regardless, if you need to run Apache 2, and you run it in pre-fork mode, you should be fine. Hope that helps. Chris = Chris Shiflett - http://shiflett.org/ PHP Security Handbook Coming mid-2004 HTTP Developer's Handbook http://httphandbook.org/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP and Apache 2 (Was: Ver 5.0 Questions ...)
Mark Charette wrote: > If you read through the archives you'll find it isn't so much that > PHP is the problem per se, but many of the PHP modules. If you use the > multi-threading model of Apache 2 (the raison d'etre for using > Apache 2 for > most people) then all the modules have to be thread-safe, and that's a > non-trivial matter for many of the module authors and maintainers. If > you use the pre-fork model of Apache 2 then you essentially have the > "regular" version of Apache. I am using the pre-forked model in Apache2 yes. So far I haven't noticed any problems with PHP(4/5beta). If the problems with PHP is with the non pre-forked models, then its time to update the recommendation to not run PHP on Apache2. Instead it should explain why it doesn't work and that if pre-forked is used there are no problems. Since this problem is known maybe even modules that cause the problems could be indicated as non pre-forked compatible. After all I might not need any of them and could thus use a non pre-forked model for PHP. As I understand this is not a recently discovered problem. Therefore I wonder what is done to fix the modules not working properly. Is it possible to fix for all modules? Even though PHP is very popular, and gaining more and more popularity at all levels, this is a potential show stopper. This comes with a performance loss (can't imagine anything else since it is a major new feature in Apache2) and thus a negative "thing" for PHP. /Thomas -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
