This is the mail archive of the firstname.lastname@example.org
mailing list for the Cygwin project. See the Cygwin
home page for more information.
Re: B20.1: Scripts not executed in the current directory (bash)
- To: Chris Faylor <email@example.com>
- Subject: Re: B20.1: Scripts not executed in the current directory (bash)
- From: Ares <firstname.lastname@example.org>
- Date: Fri, 9 Apr 1999 15:25:01 -0500 (CDT)
- cc: dye053 <email@example.com>, firstname.lastname@example.org
Or you can invoke the script (or any other executable) with ./foo.pl. I
can't speak much for the Cygwin world, but in the Linux world, this is SOP
for security reasons.
Jason D. Michaelson | Debian GNU/ o http://www.debian.org
email@example.com | _
firstname.lastname@example.org | / / _ _ _ _ __ __
Jason.D.Michaelson@cdc.com | / /__ / / / \// //_// \ \/ /
| /____/ /_/ /_/\/ /___/ /_/\_\
~mich0101 | ...because lockups are for convicts...
And the beast shall come forth surrounded by a roiling cliud of
vengeance. The house of the unbelievers shall be razed and they shall
be scorched to the earth. Their tags shall blink until the end of
days. -- The Book of Mozilla, 12:10
"One World, One Web, One Program." -- Bill Gates
"Ein Volk, Ein Reich, Ein Fuhrer." -- Adolph Hitler
On Fri, 9 Apr 1999, Chris Faylor wrote:
> On Fri, Apr 09, 1999 at 02:18:22PM -0500, dye053 wrote:
> >In B20.1 I noticed a problem that I didn't have with B20 release:
> >In bash, scripts with shebang (#!) are not excuted in the current
> >directory, although they are correctly identified as executable files by
> >ls. On the other hand, scripts located in a different directory are
> >executed without a problem.
> >A workaround is to call the interpreter explicitly, e.g. perl foo.pl
> >Anyone else have this problem?
> Set your PATH environment variable to include the current directory.
> Want to unsubscribe from this list?
> Send a message to email@example.com
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org