This is the mail archive of the
mailing list for the Cygwin project.
RE: 1.5.19-4 exec family of functions find wrong file to execute
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: Dave Korn <dave dot korn at artimi dot com>
- Cc: cygwin at cygwin dot com
- Date: Tue, 31 Jan 2006 09:34:20 -0500 (EST)
- Subject: RE: 1.5.19-4 exec family of functions find wrong file to execute
- References: <006501c62656$1f0f09c0$a501a8c0@CAM.ARTIMI.COM>
- Reply-to: cygwin at cygwin dot com
On Tue, 31 Jan 2006, Dave Korn wrote:
> On 30 January 2006 19:23, Martin wrote:
> > Any response?
> > TIA
> > --- Martin <linkscrazy@yahoo.!> wrote:
> >> I am attempting to invoke a command with execvp/execlp. If a file
> >> appears in my PATH before the executable desired and has the same name
> >> as the executable, the first occurrence of the file name is used as
> >> the executable to invoke. Even though the first file is NOT marked as
> >> executable.
> >> Is this normal behavior for execlp/execvp?
> >> Shouldn't the execution permission be set in order to execute it?
> Depends on your mountpoints. If the file is found under a mountpoint
> with the cygexec flag set, it will be assumed to be executable
> regardless of the x bit in the file's perms.
Also, on FAT filesystems, there are no permission bits[*]... Your file
may be tripping the executable file detection heuristics, though.
[*] Cygwin can simulate them for you on pure FAT with "ntea", but with
FAT32 you're SOL.
|\ _,,,---,,_ firstname.lastname@example.org | email@example.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html