For several days I’ve been trying to compile the required installers for a project which used debian based package. Iang’s code really helps, try it out. The problem is, apache2 and php5 package seems had a little conflict.
apache2 has apache2-mpm-worker_2.2.9-7ubuntu3_i386.deb which is: (http://packages.ubuntu.com)
Each Apache Multi-Processing Module provides a different “flavor” of web server binary, compiled with a different processing model.The worker MPM provides the default threaded implementation. It is recommended especially for high-traffic sites because it is faster and has a smaller memory footprint than the traditional prefork MPM.
and php5 has apache2-mpm-prefork_2.2.9-7ubuntu3_i386.deb which is:
The prefork MPM provides a non-threaded, pre-forking implementation that handles requests in a manner similar to Apache 1.3. It is not as fast as threaded models, but is considered to be more stable. It is appropriate for sites that need to maintain compatibility with non-thread-safe libraries, and is the best MPM for isolating each request, so that a problem with a single request will not affect any other.
And in the end you must replace the worker with the prefork version or it’ll conflict. So the question is why? What if I need to deploy them into production?
And why I don’t have this kind of conflict problem if i use apt-get install php5 apache2 instead.
March 27, 2009 at 8:26 am
any specific reason why you want run mpm-worker instead of mwm-prefork?
check this: http://tinyurl.com/c85×4h
March 27, 2009 at 9:32 am
interesting! i should’ve RTFM first
March 28, 2009 at 5:14 pm
http://fajran.web.id/story/2005/02/24/apache2-dan-php-di-debian
*siyul siyul*
March 28, 2009 at 7:52 pm
holy crap xD
April 7, 2009 at 3:04 pm
Holy.. wood.
April 7, 2009 at 3:11 pm
knp ni orang ngga jelas, udah bisa browsing lagi lo?