On 25 Feb 2011, at 13:58, Achikbache Guilhem wrote:
>> That's not a bug at all. You can't expect to run the mod_php5 plugin
>> and mod_suphp at the same time.
>
> Actually, you can! I have already shared my config on using mod_php and
> mod_suphp at the same time.
I didn't say it wasn't possible, I said you can't expect it; meaning that it
won't work "out of the box".
> I think it is required (on debian at least) because phpmyadmin and all other
> system wide web apps would be run as root... and then must be handled by
> mod_php and not suphp.
It isn't _required_ to configure any particular way. phpmyadmin will run
equally well under mod_php as it will under fcgi+php as it will under cgid+php
as it will under suphp.
> The whole point is about activating mod_suphp *before* mod_php, because
> mod_suphp can be disabled at runtime, not mod_php;
that isn't a requirement either, as you can just set suphp to listen as a
different handler to the default (or reconfigured) mod_php handler mapping.
> if mod_php is
> configured first, it will handle all x-application-php types. But you
> can configure suphp to be enabled for vhosts only.
or, as I said above, configure suphp to handle different mime-types. suPHP can
be configured for "vhosts only", as can mod_php; there is no difference there.
Regards,
The Honeymonster aka Daniel Llewellyn - [email protected]
_______________________________________________
suPHP mailing list
[email protected]
https://lists.marsching.com/mailman/listinfo/suphp
