thats what I thought initially, but being that it runs fine from the command line, wouldn't that indicate that it can be resolved. The only thing I can think of is some sort of apache.conf issue | [reply] |
The webserver (apache/httpd) runs as some user (ex apache) which is not the same user (you) in the shell,
so permissions can be different, %ENV ....
| [reply] |
That makes sense... but what is the differences? The paths?
CGI
PATH = /sbin:/usr/sbin:/bin:/usr/bin
shell
PATH = /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
I assume it can read the perl modules ok, but it can't either resolve the DNS (where is that done??), or access out is blocked for the apache user (how do I check that?).
Thanks in advance.
| [reply] |