On Tue, 26 Feb 2002, Alan Mead wrote:
>Is the file format dos or unix? An easy way using vi (you may be deluged
>with alternatives) is to edit the file (e.g., 'vi scriptname.pl'), then type
>':set fileformat=unix', then enter, then write the file (':wq' or 'ZZ' will
>write and quit). I have fou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Archer wrote:
>I sometimes have a problem running downloaded perl scripts. If I type
>something like "perl scriptname.pl" for one of these problem scripts, it
>runs fine. When I try "./scriptname.pl" I get the following:
>
>bash: ./scriptname.p
Is the file format dos or unix? An easy way using vi (you may be deluged
with alternatives) is to edit the file (e.g., 'vi scriptname.pl'), then type
':set fileformat=unix', then enter, then write the file (':wq' or 'ZZ' will
write and quit). I have found that newline differences can confuse per
I have had the same problem on some occasions. What caused the problem in my
case was when the scripts were edited by oops I have to say it m$ notepad or
the like. This seemed to put some hidden characters in the text which made
the interpreter real grumpy. Same thing happened to my rc.firewall sc
