It was the ^M at the end of the shebang line that was causing things to fail. Seems
someone
uploaded a zipped file and extracted the archive without bothering to fix the line
endings!
Cheers,
Curtis Poe
=
Senior Programmer
Onsite! Technology (http://www.onsitetech.com/)
"Ovid" on http://w
On Mon, 20 Aug 2001, Curtis Poe wrote:
> Just verified that there *is* a ^M at the end of the shebang (seems
> that someone unzipped a script rather than using FTP), but then our
> colo went down, so I can't test that this is causing the problem.
> However, I just tested it under Cygwin and the ^
--- Jeff 'japhy/Marillion' Pinyan <[EMAIL PROTECTED]> wrote:
> I'd say that you've got a ^M at the end of the line.
>
> cat -vet somescript.cgi
>
> will tell you for certain.
Just verified that there *is* a ^M at the end of the shebang (seems that someone
unzipped a script
rather than using
So, if you take out the -w but leave in the -T it still will not run?
-Original Message-
From: Curtis Poe
To: [EMAIL PROTECTED]
Sent: 8/20/2001 5:17 PM
Subject: Turning off warnings causes scripts to fail
Time for me to ask a question instead of answering one. I'm having a
pr
On Aug 20, Curtis Poe said:
>One of our scripts runs fine from the command line but wouldn't run
>through the browser. We'd type
>
>perl somescript.cgi
>
>and everthing would run fine.
>
>However, when we tried
>
>./somescript.cgi
>
>we would get a "No such file or directory" error. The s
Time for me to ask a question instead of answering one. I'm having a problem with a
shebang line
and multiple versions of Perl.
One of our scripts runs fine from the command line but wouldn't run through the
browser. We'd type
perl somescript.cgi
and everthing would run fine.
However, w
