Beats All I've Seen

[iggit]

Ok here we are: Scripts that had been working just fine on both a build server and a test server are now installed on the primary box, with ExecCGI granted. Scripts work if they are cut with with an exit before doing any if/then functions. If no cut off is made the scripts never load and hang. In running Scriptest.cgi on them, there are no syntax errors anywhere. What in the world is doing this? any ideas? Please?

 

[Leland123]

Hi ggit,

Are you running windows, linux, unix, etc. If you have a double quote open, it can cause perl of hang. You might try running the offending script from the command line to see if perl will help you with any debugging info or the number of the line that is causeing the problem. If your script were named test_script you could run it from the command line like:

perl test_script.pl

Sometimes this will generate error message that do not show in the web browser.

LelandJ


Leland F. Jackson, CPA
Software - Master (TM)

http://www.smvfp.com

Nothing Runs Like the Fox

 

[Coderifous]

use strict;
use warnings;
use diagnostics;


These need to go at the top of your script.

Then run it. See if you get any good stuff back... no?

perl -d script.pl (the debugger (cmd line))

--jim