Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

apache problem



On 11/26/2010 08:41 PM, Jerry Feldman wrote:
> On 11/26/2010 07:36 PM, j. daniel moylan wrote:
>> dan kressin writes:
>>> --- On Wed, 11/24/10, j. daniel moylan-/E1597aS9LQAvxtiuMwx3w at public.gmane.org <j. daniel moylan-/E1597aS9LQAvxtiuMwx3w at public.gmane.org> wrote:
>>>> did this -- unfortunately, same result -- restarted htppd,
>>>> then rebooted -- no change.
>>>>
>>>>   Options MultiViews Indexes FollowSymLinks
>>>> IncludesNoExec
>>> What are the permissions on the dir/file the symlink points
>>> to?  What error do you see in the browser?  Is there
>>> anything in the Apache access and/or error logs?
>>> (/var/log/httpd/{access,error}.log, typically)
>> ha!!  my bad -- the sym links pointed to stuff in my home
>> directory, and though all my directory permissions were
>> fine, i hadn't noticed that /home itself was set to 700
>> (new operating system installation)!  i changed that to
>> 755 and all is well.
> This is standard. In a multi-user system, you want peoples' home
> directories to be rww owner with no perms for anyone else.

Yeah, if this is really a system that only you touch, that's OK to do,
but in general you want to set up a completely separate directory with
you as the owner and apache (or www-data or httpd or whoever runs
Apache) as the group.  Then make it grup-readable but not writable.






BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org