SuExec wants a configure parameter specifying its execution path. You mostly want this to be the document root of the running webserver. The Gentoo ebuild file hardcodes "/var/www" as the base dir of suexec. If you want to use another document root e.g. /srv or /home, you must edit the ebuild file. We did do this with a script that does emerge sync and then modified the apache-2 ebuild files. Now, as of 2.0.54, the apache ebuild files are digest protected and we always get a digest mismatch. :-/ Doing ebuild .../apache-* digest every time is not really a good solution. I think the apache ebuild file should look for either a variable from make.conf or a config file to set this path correctly.
(In reply to comment #0) > SuExec wants a configure parameter specifying its execution path. You mostly > want this to be the document root of the running webserver. > > The Gentoo ebuild file hardcodes "/var/www" as the base dir of suexec. If > you want to use another document root e.g. /srv or /home, you must edit the > ebuild file. > [...] We're in the process of fixing this (well, I've started an eclectic module to a suexec-config tool, which I'm hoping we'll take official someday). Either way, we have to get the 'apache refresh' updates stable before we go adding new features like this, that may break a working suexec. Resolving LATER, will pick this up again once got the above mentioned updates stable.
*** Bug 99118 has been marked as a duplicate of this bug. ***
This should be reopened.
