700 would only be right if the the directories and files are all owned by the user that the webserver processes run as (not the root process, but the others that are spawned to actually service requests.
Example: if I issue:
ps auxwww | egrep httpd
I get:
root 2730 0.0 0.4 19776 2496 ? S Jul31 0:01 /usr/sb +in/httpd apache 2763 0.0 0.5 19840 2692 ? S Jul31 0:00 [httpd] apache 2764 0.0 0.5 19848 2700 ? S Jul31 0:00 [httpd] apache 2765 0.0 0.5 19840 2696 ? S Jul31 0:00 [httpd] apache 2766 0.0 0.5 19916 2816 ? S Jul31 0:00 [httpd] apache 2767 0.0 0.5 19924 2840 ? S Jul31 0:00 [httpd] apache 2768 0.0 0.5 19800 2564 ? S Jul31 0:00 [httpd] apache 2769 0.0 0.4 19800 2468 ? S Jul31 0:00 [httpd] apache 2770 0.0 0.4 19800 2468 ? S Jul31 0:00 [httpd]
so you should check that the apache user (or whatever user is involved in your case) has access to the files, by issuing: su - apache (if you do this from other than root, you'll be promted to enter the password for the apache account), the attempt to run/compile the modules with perl -cw /home/homedir/www/module.pm (or is it perl -cw /home/homedir/www/perl/module.pm?)
--Bob Niederman, http://bob-n.comIn reply to Re: mod_perl setup problems
by bobn
in thread mod_perl setup problems
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |