Ya, I think there is a setting in Apache's conf file, but it has been quite some time that I have been mucking with apache.
Note, that most often when you can run it from the command line and it doesn't work from http, there is usialy a permissions issue. Although I have never experianced issue with modules in my @INC.
| [reply] |
I thought about a permission's issue as well but the error message didn't state an error opening or executing. I looked through my httpd.conf and couldn't find anything that instructed apache to use a specific program or user to execute cgi scripts but that doesn't mean the directive isn't supported. I suppose the OP could "su - username" to the user that runs the cgi scripts and test it from the command line. In my experience that user is usually "apache" or "nobody".
| [reply] |
I get hit by a similar problem occasionally. I would definitely check the permissions on the installed module. When I install as root, I sometimes forget to drop my umask from 077 (my paranoid default) to 022 (so that non-root users can read/execute stuff installed). Also look in architecture-specific subdirectories. (i.e., at work when I mess this up, I've got to check solaris4-multi-thread, or whatever, and at home, i686-linux subdirs).
Update: The reason the error message doesn't indicate anything about reading or executing is because it couldn't find the file, as the permissions on the directory containing the .pm are too strict. Example:
| [reply]
[d/l] |
