My mistake. I misread the orginial message. It was referring to the
/home/USER directory, not the /home/USER/public_html directory.
If you set /home/USER to 701, and /home/USER/public_html to 755, then
everything is works great and things stay more secure than having
/home/USER 755.
Double
> "RL" == Robert Landrum <[EMAIL PROTECTED]> writes:
RL> Under Linux, 'x' does mean execute... from the chmod manpage
RL> The letters `rwxXstugo' select the new permissions for the
RL> affected users: read (r), write (w), execute (or access
RL> for directories) (x
Neither of the following combinations worked for me:
drwx--x--x3 rlandrum devel4096 Jan 30 14:14 public_html
(711, Forbidden)
drwx-x3 rlandrum devel4096 Jan 30 14:14 public_html
(701, Forbidden)
The only one that worked was:
drwxr-xr-x3 rlandrum devel4096
> 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 al
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).
Robert Landrum
>Hi folks,
>
>Maybe I'm just rusty after 8 months off, but my StatINC can't find
>files that exist on the sy
Hi,
do you have a startup.pl with something like
$ENV{MOD_PERL} or die "not running under mod_perl!";
use lib qw( /your-path-to-your-libs );
which is registred in your httpd.conf with something like
PerlRequire /etc/httpd/startup.pl
PerlInitHandler Apache::StatINC
