There are regular reports on the Horde/IMP lists that PHPs gettext component is broken. As the other poster says, this is some how thread related; PHP not being thread safe. There is at least one report of languages that change within a single page... But it seems that this only happens under heavy load.
It would be interesting to know if PHP 5 will be thread safe, and this usable in production with Apache 2.x
Even if PHP were 100% threadsafe, it generally uses too many libraries for it to be practical to make sure they're ALL threadsafe.
Actually the PHP core is 100 percent threadsafe now, it is only specifically the external libraries which aren't.
If you use PHP w/FastCGI support you wont run into these issues. If you only compile MySQL or Postgres support into your PHP you wouldn't either. But many users frequently also compile in other external libs for things like graphics generation, url manipulation, etc and its these libraries which aren't thread safe and specifically can cause problems in high use environments.
While you could specifically use PHP and Apache2 in total prefork mode, this basically makes it run exactly like the 1.3 series, so then the real question is what's the point of upgrading at all and not just sticking w/1.3?
While you could specifically use PHP and Apache2 in total prefork mode, this basically makes it run exactly like the 1.3 series, so then the real question is what's the point of upgrading at all and not just sticking w/1.3?
Because some servers like the subversion apache module require apache2, and I'd like to not have to run both apache1.3 and 2 in parallel. I am curious as to why the php documentation doesn't mention that using the prefork mpm and php would work fine however.
Given that Apache development is predictably going to continue on the 2.0 branch (which is a questionable point of departure), keeping your site secure with minimum maintenance cost requires using binary releases on the 2.0 platform for web applications.
If you only compile MySQL or Postgres support into your PHP...
You know what? I've been trying to do this very thing for two days now and I can not get Apachetoolbox to compile a pgsql.so so I can have a working PHP installation w/ pgsql support. I have to have this tomorrow and I can not find any place that makes any mention of this. It is ubber annoying. This one stinkin' little shared library is holding up the entire project.:-(
Well I'm not too familiar with Apachetoolbox, but if you just compile Postgres with default options it will pretty much generate a.so that it places under $PREFIX/lib/plpgsql.so
Thanks for the reply. That's not the.so I'm after. The one I'm trying to get compiled is the PHP shared library that PHP loads for pgsql support, pgsql.so ATB is a really handy program that makes it quick and easy to compile and install any number of known Apache modules and accessories. No muss no fuss. Apache gets preconfigured for it and all. That's the pretty intro to it. The other side of the coin is that it doesn't always work. I'm going to have to dump it one of these days and go back to bui
"There are things that are so serious that you can only joke about them"
- Heisenberg
I've been running PHP/Apache 2 for a while... (Score:4, Interesting)
...and haven't noticed any problems. Why is this advised against?
Re:I've been running PHP/Apache 2 for a while... (Score:4, Informative)
It would be interesting to know if PHP 5 will be thread safe, and this usable in production with Apache 2.x
Re:I've been running PHP/Apache 2 for a while... (Score:3, Informative)
Even if PHP were 100% threadsafe, it generally uses too many libraries for it to be practical to make sure they're ALL threadsafe.
Re:I've been running PHP/Apache 2 for a while... (Score:5, Informative)
Actually the PHP core is 100 percent threadsafe now, it is only specifically the external libraries which aren't.
If you use PHP w/FastCGI support you wont run into these issues. If you only compile MySQL or Postgres support into your PHP you wouldn't either. But many users frequently also compile in other external libs for things like graphics generation, url manipulation, etc and its these libraries which aren't thread safe and specifically can cause problems in high use environments.
While you could specifically use PHP and Apache2 in total prefork mode, this basically makes it run exactly like the 1.3 series, so then the real question is what's the point of upgrading at all and not just sticking w/1.3?
Re:I've been running PHP/Apache 2 for a while... (Score:3, Informative)
Because some servers like the subversion apache module require apache2, and I'd like to not have to run both apache1.3 and 2 in parallel. I am curious as to why the php documentation doesn't mention that using the prefork mpm and php would work fine however.
Re:I've been running PHP/Apache 2 for a while... (Score:2)
going to continue on the 2.0 branch (which is
a questionable point of departure), keeping
your site secure with minimum maintenance cost
requires using binary releases on the 2.0
platform for web applications.
Re:I've been running PHP/Apache 2 for a while... (Score:2)
You know what? I've been trying to do this very thing for two days now and I can not get Apachetoolbox to compile a pgsql.so so I can have a working PHP installation w/ pgsql support. I have to have this tomorrow and I can not find any place that makes any mention of this. It is ubber annoying. This one stinkin' little shared library is holding up the entire project. :-(
Re:I've been running PHP/Apache 2 for a while... (Score:1)
Re:I've been running PHP/Apache 2 for a while... (Score:2)