Previously in this thread: I couldn't get Apache to serve pages that were perl scripts. I thought that I had added the correct incantations to the various Apache .conf files, and it still didn't work.
I called out to this list for help, and many replied (Thanks!), the consensus being that I had a permissions problem. I had confessed to being a bit fuzzy about file/dir permissions, and a few of you wrote me some very useful mini-tutorials (Thanks again!). Some of the permissions stuff I already understood, and other parts we quite instructional. But when I applied it all to my Apache/perl problem, it still wouldn't work. It seemed that the permissions were set OK. Now: I think I've figured it out. On rereading the Apache CGI config docs, I see now that it says that if suEXEC is enabled it does some sort of stricter permissions checking, and that that could be a problem. I looked into this, and Eureka! All the symptoms were there. The suexec log had this line: [2002-02-20 17:09:57]: cannot get docroot information (/home/jgh) I spent a little time trying to figure out how to get it to "get docroot information" but I couldn't puzzle it out quickly, so I fell-back on the suggested Plan B. I disabled suEXEC. And now everything works fine now!!! Yay! But now here's my new question for the group: Was disabling suEXEC an OK idea? Have I opened up some hole? or turned off some otherwise useful function? I think I know what suEXEC does, and I don't think I need it, but I'd like a REALITY CHECK. Please let me know. Thanks. -- Jack Hodgson <[EMAIL PROTECTED]> ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
