Re: Re: rexec from a cgi vs cmdline

I just had a similar problem myself and found out the problem was linked to two installations of Perl on the same machine, in different directories, with different @INC. The @INC from the command line and the @INC from the CGI were different, and voila. The key is to go to /usr/bin/ (or wherever your main installation is) and do a ./perl -MCPAN -e shell to make sure the modules are installed in the proper @INC. (Of course, you could always just move the modules around manually, but I prefer the easy way. :-D)

Gary Blackburn
Trained Killer

Comment on Re: Re: rexec from a cgi vs cmdline Download Code

Replies are listed 'Best First'.
Re: rexec from a cgi vs cmdline by dataDrone (Acolyte) on Aug 18, 2001 at 18:03 UTC
Ok, Last night i printed out the @INC's from a cgi triggered script and from root's command line and found them to be identical. I then searched through the @INC paths and found the Rexec.pm nodule and checked it's permissions. It is world readable. I didn't (yet) check all the directories leading up to that but will as soon as i get a chance to telnet (SSH) into work (the box in question). In the mean time i'll try the whole shebang on the laptop (which has a very similar install of Linux) and see if it works or not. Thanks for the efforts, Dan.	[reply]

Replies are listed 'Best First'.

Re: rexec from a cgi vs cmdline
by dataDrone (Acolyte) on Aug 18, 2001 at 18:03 UTC

Ok, Last night i printed out the @INC's from a cgi triggered script and from root's command line and found them to be identical. I then searched through the @INC paths and found the Rexec.pm nodule and checked it's permissions. It is world readable. I didn't (yet) check all the directories leading up to that but will as soon as i get a chance to telnet (SSH) into work (the box in question). In the mean time i'll try the whole shebang on the laptop (which has a very similar install of Linux) and see if it works or not. Thanks for the efforts, Dan.

[reply]