I do as of yesterday, and still don't know a cure. Anyone else figure this out?Anyone?
Surely someone out there must need both of them!
Why do you need mod_perl?
Most server configurations have no need for mod_perl because you
do not need it in order to run and fully support Perl scripts.
In the same vain, there are better ways to run PHP than as a plain
insecure Apache module. I personally would recommend SuPHP
for those on Apache 2 but if you aren't on Apache 2 then you might
want to consider phpSuExec.
Bottom line though it is extremely rare for you to actually legitimately
need both mod_perl and mod_php so I am a bit curious as to what
you are specifically wanting to do on the server that needs those.
Most server configurations have no need for mod_perl because you
do not need it in order to run and fully support Perl scripts.
In the same vain, there are better ways to run PHP than as a plain
insecure Apache module. I personally would recommend SuPHP
for those on Apache 2 but if you aren't on Apache 2 then you might
want to consider phpSuExec.
Bottom line though it is extremely rare for you to actually legitimately
need both mod_perl and mod_php so I am a bit curious as to what
you are specifically wanting to do on the server that needs those.
I wanted to evaluate the trial version of @Mail, and it requires mod_perl. They are supposedly putting out a PHP version, and so now I'm going to wait for that.
I didn't know Apache2 was on a stable release, or are you running on an edge release?
I have a customer who needs mod_perl for a site he's migrating to his VPS.
It does no good for you to ask why... the poster was asking for people who have attempted to set this up. Not suggestions on how we can get around setting it up.
I'd be grateful to anyone with more information on this topic as well!
Thanks!
It does no good for you to ask why... the poster was asking for people who have attempted to set this up. Not suggestions on how we can get around setting it up.
I'd be grateful to anyone with more information on this topic as well!
Thanks!
it is/was likely an incompatibility with the implementation in the easyapache in Current, Release and Stable. I don't see any such warning (other than: you need to know what you are doing) when enabling mod_perl and mod_php in the new easyapache (EA3) in Edge.