On Wed, 9 Oct 2002 13:47:56 -0400
Chris Herrnberger
How is SuSE setting up apache to serve public_html files?
set the /home/testuser/public_html/index.html path to chmod -R 744 and added the user <testuser> to the group <nogroup>
You don't need to add the testuser to "nogroup" This is the way it works: 1. The apache server will start suexec for the home directories, if it finds it. It's in /usr/sbin/suexec. Now suexec will let apache run as <testuser><users> in testuser's public_html directory. This is different from the way apache normally runs as <nobody><nogroup>. Now suexec puts alot of restrictions , and it checks all cgi files, and will refuse to run them if the permissions are off. You need to read the apache docs on suexec. It allows you to run your public_html as mode 700, but it is more dangerous, because it lets people come into your public_html as the user, instead of nobody. In the main server httdocs and cgi-bin, apache will run as <nobody><nogroup>; SuSE uses a user called wwwrun instead of nobody, but it's about the same. So you may want to rename suexec to disable it, unless you want to read up on it. Your testuser should be in group users. There is a suexec log in the /var/log/httpd logs, it will give you some clues.
http://testsite/~testuser give me no access permission error???
Change your testuser back into group users, and make your cgi scripts 755, and your html 644. Then either turn off suexec or check the suexec log.
So what am I doing wrong. Something probably very obviouse to another pair of eyes.
-- use Perl; #powerful programmable prestidigitation