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/
