This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: FAQ or bash bug with ntsec? (WAS: Help request: bash with PATH problems)
- From: "John Morrison" <john dot r dot morrison at ntlworld dot com>
- To: "'Cygwin-List'" <cygwin at sources dot redhat dot com>
- Date: Tue, 30 Jul 2002 09:50:13 +0100
- Subject: RE: FAQ or bash bug with ntsec? (WAS: Help request: bash with PATH problems)
*Many* thanks for solving this. I run 3 copies of cygwin; desktop
at home, laptop and desktop at work. The desktop at home showed
this issue and I was unable to figure out why.
Could this be put in a FAQ somewhere please?
J.
> From: Schaible, Jörg
>
> Hello all,
>
> lately I found the reason for this odd behaviour that my path is
> ignored in
> bash. The main reason causing it was the activation of ntsec in my new
> profile. After activation /bin/find.exe has follwing settings:
>
> $ ls -l /bin/find.exe
> -rwx------ 1 admins nobody 78848 20. May 05:39 /bin/find.exe
>
> while the other find has:
>
> $ ls -l /cygdrive/c/WINNT/system32/find.exe
> -rwxrwxr-x 1 admins system 10000 4. May 2001
> /cygdrive/c/WINNT/system32/find.exe
>
> bash will find and execute with ntsec always
> /cygdrive/c/WINNT/system32/find.exe independently where the path for
> /cygdrive/c/WINNT/system32 is in the PATH! Applications
> applications in /bin
> will be found and executed if there is no other executable with same name
> (behaviour does not apply to more.exe/more.com) with a "better" ACL.
>
> After changing owner and group of the files and a restart of the shell,
> /bin/find.exe is found first and the system behaves as expected! Note: The
> behaviour could only be observed for bash, any other shell on my system
> (ash, tcsh, zsh, cygtclsh80) did not have this problem.
>
> Regards,
> Jörg
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/