in reply to Re^5: Testing scripts
in thread Testing scripts

Double-check your host's docs for any information about the location of their perl binary. There's a strong chance that it may be at /usr/bin/perl rather than /usr/local/bin/perl, since it would have been installed as part of the operating system instead of a "local" addition. If that path is wrong, then it doesn't matter if your Perl is perfect because the web server process won't be able to find the perl binary to execute it.

Replies are listed 'Best First'.
Re^7: Testing scripts
by zealf (Novice) on Feb 13, 2010 at 12:09 UTC
    Good point, this code however I was testing on my own Win machine with a command line. My host's cpanel lists
    /home/themanin/perl #as the path to use #the following is used within the script. BEGIN { my $base_module_dir = (-d '/home/themanin/perl' ? '/home/themanin/ +perl' : ( getpwuid($>) )[7] . '/perl/'); unshift @INC, map { $base_module_dir . $_ } @INC; } #although in saying this the FAQ side advises... * Path to Perl: /usr/bin/perl * Path to Sendmail: /usr/sbin/sendmail * Home Directory: /home/your_username/
    I'm slowly narrowing things down here. The latest error I"m getting is
    [Sat Feb 13 04:01:14 2010] [alert] [client 119.12.114.196] /home/thema +nin/public_html/cgi-bin/.htaccess: Invalid command '+ExecCGI', perhap +s mis-spelled or defined by a module not included in the server confi +guration
    I'm sinking, help help. lol