Daniel Andersson:
>
> # aptitude install php5
> The following NEW packages will be installed:
> apache2-mpm-prefork{ab} libapache2-mod-php5{a} libonig2{a}
> libqdbm14{a} php5 php5-cli{a} php5-common{a} php5-suhosin{a}
> 0 packages upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
> Need to get 6,654 kB of archives. After unpacking 17.3 MB will be used.
> The following packages have unmet dependencies:
> apache2-mpm-prefork: Conflicts: apache2-mpm which is a virtual package.
> apache2-mpm-worker: Conflicts: apache2-mpm which is a virtual package.
> The following actions will resolve these dependencies:
>
> Remove the following packages:
> 1) apache2-mpm-worker
There is no problem here, as Javier already suggested. Aptitude simply
tells you that your current Apache MPM ("multi-processing module") is
incompatible with PHP and at the same time proposes to use another MPM
that works with PHP.
Background: Apache supports several modes of parallelism. The "worker"
MPM runs multithreaded, while prefork uses processes instead of threads.
AFAIK PHP doesn't work in a multithreaded environment and that's why you
have to use the prefork MPM. You probably won't notice any difference,
except that you are going to have more apache2 processes running than
before.
J.
--
A passionate argument means more to me than a blockbuster movie.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>
signature.asc
Description: Digital signature
