On 8/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Definitely not all that clear...I don't suppose there's a runtime way to
fix this...I dread possibly breaking all my module installs by
recompiling...
The only runtime fix would be moving all your vhosts under the suexec docroot.
But re
On Mon, 28 Aug 2006, Joshua Slive wrote:
> On 8/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > I checked the Apache docs on SuExec and found this:
> >
> > "--with-suexec-docroot=DIR
> > Define as the DocumentRoot set for Apache. This will be the only
> > hierarchy (aside from User
On 8/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi:
After running Apache 1.3.x with SuExec for many years, I just upgraded to
2.2.3. I installed it from FreeBSD ports with SuExec enabled, but without
specifying much else, figuring I could change that runtime.
After making the neccess
Hi:
After running Apache 1.3.x with SuExec for many years, I just upgraded to
2.2.3. I installed it from FreeBSD ports with SuExec enabled, but without
specifying much else, figuring I could change that runtime.
After making the neccessary changes in my virtual host users' conf file
(changing U
