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 shebang line was >#!/usr/bin/perl and sure >enough, there is a /usr/bin/perl out there. I'd say that you've got a ^M at the end of the line. cat -vet somescript.cgi will tell you for certain. -- Jeff "japhy" Pinyan [EMAIL PROTECTED] http://www.pobox.com/~japhy/ RPI Acacia brother #734 http://www.perlmonks.org/ http://www.cpan.org/ ** Look for "Regular Expressions in Perl" published by Manning, in 2002 ** -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Turning off warnings causes scripts to fail
Jeff 'japhy/Marillion' Pinyan Mon, 20 Aug 2001 14:57:31 -0700
- Turning off warnings causes scripts to fail Curtis Poe
- RE: Turning off warnings causes scripts... Jeff 'japhy/Marillion' Pinyan
- RE: Turning off warnings causes scripts... Gibbs Tanton - tgibbs
- RE: Turning off warnings causes scr... Curtis Poe
- Re: Turning off warnings causes scripts... Curtis Poe
- Re: Turning off warnings causes scr... Brett W. McCoy