As root you can see the PATH variable for any running process in the
/proc directory. Here is what you need to do:
1. su to root
2. run the command ps -e | grep httpd which will show you all of
process ids for apache
3. cd to /proc and do an ls. You should see a directory with the same
On 10 feb 2007, at 19.23, Steve Pelikan wrote:
We have several perl cgi scripts that run fine with apache 2.0 but
fail with 2.2. This is using 2.2 that is part of recent Fedora and
2.0.59 that I just built and installed on the same machine.
The problem seems to be with system() calls in pe
> Just having suexec loaded shouldn't make any difference because(AFAIK)
> it isn't actually used unless you explicitly request its use.
Good point.
Okay, in a perl cgi script run by version 2.2 the command system("ls")
returns an error code (256, as I recall which corresponds to actual
exitcod
Just having suexec loaded shouldn't make any difference because (AFAIK) it
isn't actually used unless you explicitly request its use.
Putting a "print" statement before the call to system(ls) doesn't tell us
anything about whether or not the running program can *find* the ls command
in order to e
Thanks. It is finding and executing the scripts. (Can put in a print
statement before the system() command and see the results on a web
browser calling the script.
Both the 2.0 and 2.2 apaches are using mod_cgi. In 2.0 it is built in
and in 2.2 there's a LoadModule statement for it in httpd.
Being in the same directory as the program that is running is no guarantee
that the command will be found, unless you either have "." in the PATH, or
the language your command is written is explicitly looks in the same
directory as the running program when resolving commands.
On 11/02/07, William
Steve Pelikan wrote:
> We have several perl cgi scripts that run fine with apache 2.0 but fail
> with 2.2. This is using 2.2 that is part of recent Fedora and 2.0.59
> that I just built and installed on the same machine.
>
> The problem seems to be with system() calls in perl.
>
> What am I'm mis
Perhaps I wasn't clear. ANY script with a 'system()' command fails to
run as a gci script under apache 2.2. Even if the command that is being
run is in the same directory as the script (/var/www/cgi-bin) and has
777 permissions.
And the same script does run under apache 2.0.
For both apache
L PROTECTED] CGI differences in apache 2.0 and 2.2
We have several perl cgi scripts that run fine with apache 2.0 but fail
with 2.2. This is using 2.2 that is part of recent Fedora and 2.0.59 that
I just built and installed on the same machine.
The problem seems to be with system() calls in p
My only experience with apache under linux is with redhat, so there may be
subtle differences.
In order to execute "ls" then the userid:group under which apache runs needs
at least two things:
1. Execute access to the executable (typically /bin/ls)
2. To have the path to the executable (/bin
We have several perl cgi scripts that run fine with apache 2.0 but fail
with 2.2. This is using 2.2 that is part of recent Fedora and 2.0.59
that I just built and installed on the same machine.
The problem seems to be with system() calls in perl.
system("ls"); returns an error with version 2.
11 matches
Mail list logo
