From: Reini U. <ru...@x-...> - 2005-01-18 08:32:43
|
Joel Uckelman schrieb: >>I had a play with apache2.0, php4.3.11 and mysql4.0.23 on windows. What I >>found was that attempting to create a virgin wiki reliably crashed the >>apache process with no info in the logs. > > It crashed Apache? Yow! Does that mean that it's an Apache bug? I didn't > think that PHP was supposed to be able to do that. Since php is loaded as shared module it is able to crash the parent process. It happens all the time on certain php bugs. Sessions exceeding ~4000 bytes, certain hairy pcre pieces (fixed recently), recent 4.3.10 - old zendoptimizer incompatiblities, or just thread-unsafe php libs. Esp. apache2 (in the threaded worker model, old-style prefork is okay) is problematic with thread-unsafe php libs. That's why Rasmus excplictly recommends NOT to use apache2 worker model in production enviroment, together with php. "Do not use Apache 2.0.x and PHP in a production environment neither on Unix nor on Windows." -- http://www.php.net/manual/en/install.unix.apache2.php http://apache.slashdot.org/comments.pl?sid=101407&cid=8644732 http://drbacchus.com/wordpress/index.php?p=844 I personally also found the php mime-type overrides with apache2 are broken, but there are workarounds. >>I "downgraded" to apache1.3 and created the wiki. Since then my dev/test >>wiki has worked with both apache1.3 and apache2.0 (most of the time I use >>2.0). I have not made the time to trace and find out exactly why apache2.0 >>crashes -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |