This is the mail archive of the
mailing list for the Cygwin project.
Re: File mode judgement
- From: "Wu Yongwei" <adah at netstd dot com>
- To: <cygwin at cygwin dot com>
- Date: Fri, 25 Jan 2002 10:45:24 +0800
- Subject: Re: File mode judgement
Thank you for so quick a response.
Now I see. I set the environment variable CYGWIN to "ntsec" when I was
testing inetd service. Now I unset CYGWIN and solved my problem.
No, it is not good yet while even the header files and text files installed
by Cygwin itself are regarded as "executable" on setup by default.
--- Original Message from "Robert Collins"
> In the past, Cygwin seemed to judge whether a file is executable on a
> combination of suffix and content. However, today when I reinstalled
> I suddenly found that it no more did it. Now on a NTFS volume it depends
> only on file attributes.
> 1) Is it a design change?
Yes. It is much faster to look at file permissions first, and content
second. Thats what unix does. The change is activated by CYGWIN=ntsec.
> 2) Is it possible to switch back to the old behaviour?
AFAIK, no. It shouldn't be needed anyway, just use chmod to set the +x
bit on any executables you have.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html