Neither of the following combinations worked for me:
drwx--x--x 3 rlandrum devel 4096 Jan 30 14:14 public_html
(711, Forbidden)
drwx-----x 3 rlandrum devel 4096 Jan 30 14:14 public_html
(701, Forbidden)
The only one that worked was:
drwxr-xr-x 3 rlandrum devel 4096 Jan 30 14:14 public_html
(755)
I didn't try 705, but I'm pretty sure it would work.
Under Linux, 'x' does mean execute... from the chmod manpage
The letters `rwxXstugo' select the new permissions for the
affected users: read (r), write (w), execute (or access
for directories) (x), execute only if the file is a direc-
tory or already has execute permission for some user (X),
set user or group ID on execution (s), save program text
on swap device (t), the permissions that the user who owns
the file currently has for it (u), the permissions that
other users in the file's group have for it (g), and the
permissions that other users not in the file's group have
for it (o).
Without the x bit, a user does not have permission to execute
anything from within the scope of that directory. Nor can the user
change into that directory.
Robert Landrum
At 10:49 AM -0800 2/6/01, Rob Bloodgood wrote:
> > wm looks like a home directory. The default perms on the home
>> directory are usually 700. Try changing that to something like 755
>> or even 744 (it may not need execute).
>
>Actually, the x bit on directory perms means "accessible," meaning if you
>KNOW the name of the file, U can reach it at all... I ran into this when
>trying to allow ~/public_html.
>
>701 is the correct mask.
>
>L8r,
>Rob
Robert L. Landrum
Senior Programmer
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"It's working correctly. It's simply working in contrast to what you have
perceived to be correct."
