As a rough guess, was that a dos/MS file? I've had very confusing scripts
like that before that couldn't find /usr/bin/perl^M, because of that control
character. If this was the case, putting -w after the invocation would fix it
as you said.
HTH
Bec
Personal reply as per your Reply-To
On Mon
> Someone suggested I check that my path includes .
> but I thought that's what the ./ was for?
Yes, you are correct and DO NOT put . in your path.
There was a "rap-on-the-fingers" thread about . in
your path. The Skinny:If a malicious person gets into
your account and puts a function named ls in
van Zyl
Subject: Re: Bash/Perl weirdness
[posted and mailed]
13 Aug 2001: "Eugene van Zyl" <[EMAIL PROTECTED]> wrote
> I've got a perl script with the following permissions:
> -rwxr-xr-x1 root root23980 Aug 13 15:55 data_update.pl
> the first line i
Hallo Eugene,
* Eugene schrieb:
> Hi,
>
> Question:
> I've got a perl script with the following permissions:
> -rwxr-xr-x1 root root23980 Aug 13 15:55 data_update.pl
> the first line in the script is:
> #!/usr/bin/perl
> which is where perl lives on Debian potato -> perl -V gives
4 matches
Mail list logo
