Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 22 Oct 2003 16:54:06 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin performance Message-ID: <20031022205406.GA26138@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3F95B7DE.90601@tlinx.org> <20031022200202.GA25720@redhat.com> <3F96EB86.5641E01D@phumblet.no-ip.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F96EB86.5641E01D@phumblet.no-ip.org> User-Agent: Mutt/1.4.1i On Wed, Oct 22, 2003 at 04:41:42PM -0400, Pierre A. Humblet wrote: >>Although, hmm. I just tried this and bash still executed a file that >>should be non-executable. I'll have to see why. > >bash walks down the PATH looking for anything that matches the name. >It remembers the first match but keeps walking until it finds an >executable. If no executable is found, it returns the first match, if >any. If it's a directory, too bad (a non-executable file can be masked >by a directory). Um, yeah but it shouldn't be able to execute a non-executable file. It's a (minor) cygwin problem. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/