My text is busy?!?!

[ido50]

Hi monks.
I got the following problem:
My CGI script, which uses strict, diagnostics and warnings, and has use CGI::Carp qw/fatalsToBrowser/ in a BEGIN block, worked great with no errors of any kind (Syntax OK), no warnings, no whatever. Anyway I did a simple change (In some string, changed from $file to $fileurl or something like that), and the script stopped working with an Internal Server Error message (The CGI::Carp doesn't catch the error). I've executed the shell script given to me by sgifford (Thank you!) and got the following message:
"+ ./downloads.pl
/path-to/errors.cgi: ./downloads.pl: text busy
+ echo Exited with status 2
Exited with status 2" where errors.cgi is the shell script in downloads.pl is the perl script in question.
I have no idea what the problem is and no idea how to fix it and I'm going crazy here. Anyone knows what might happened?!

This is the shell script by the way:

#!/bin/sh -x

printf "Content-type: text/plain\n\n";
exec 2>&1

./downloads.pl
echo "Exited with status $?"

-------------------------
Live fat, die young

[valdez]

Super Search is your friend :) Text File Busy - or not?

Ciao, Valerio

[ido50]

Thanks, the problem just went away...

-------------------------
Live fat, die young

[chromatic]

The problem is in downloads.pl, which you don't show. Undo your change, run the program from the command line with the -c flag, and fix the error there.

Without seeing the actual Perl code, there's not much to go on. If it worked before, though, and you changed something and now it doesn't work, whatever you changed broke it. Revert that.

I wouldn't rely on the error message from the shell script, as I'm not sure exit value 2 returned from Perl is meaningful across platforms. I really have no idea why that shell script would be useful.