| personaltechnologist@gmail.com 2006-02-01, 6:08 pm |
| Hi Davide!
Thanks for taking the time to answer. It's much appreciated!
>"And where is the <Directory> block referring to the DocumentRoot? "
Initially it was just the standard:
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
but in the process of troubleshooting, I added this Directory block in
case the / block didn't apply specifically to the username block:
<Directory /home/joebogus/*>
Options FollowSymLinks
Order allow,deny
Allow from all
</Directory>
[vbcol=seagreen]
>So it looks like the problem is that the FollowSymLink directive
>doesn't work for that VHost.
Yes, it sure looks that way. It's the only virtual host that had tried
to use a Symlink.
[vbcol=seagreen]
>Do you have an index.html in that directory?
Yes. I even 777'd that particular file just in case there was
something I'd forgotten. (Though I've compared this file to others in
directories that work, and they're all 644)
>Do you (by any chance) have something like SELinux enabled on that
>machine?
Actually, I do believe it *does* have SELinux enabled! I didn't set
this box up, but I believe the guy who did has set things up that way.
What are the repurcussions of SELinux being on this box interacting
with Apache and what I'm trying to do? I hope it's the culprit!
heh...
>If /home is on a different partition, is that partition mounted
>non-executable?
/home sits on a different partition from /var, though it's the same
physical drive. I had ruled that out as a potential cause though
because there are two other (functioning) virtual hosts that utilize
/home for their data. (Though neither of those two use SymLinks)
Strange how the box has two functioning virtual hosts referring to
/home and I'm unable to add another one. I even tried moving the
files from /home/joebogus to /home/joebogus/public_html and enabling
the user via the vhosts.conf file:
<VirtualHost *:80>
...
<IfModule mod_userdir.c>
UserDir public_html
UserDir disabled
UserDir enabled joebogus janebogus
</IfModule>
</VirtualHost>
with no luck...
I'm hopeful you'll be able to identify the problem as being related to
SELinux as that sounds the likely cause of what I'm seeing here. If
not though, at least you've given me a new direction to investigate,
and I appreciate it.
Thanks!
-Chris
|