This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.7 file permissions changes
- From: Eric Benson <eric_a_benson at yahoo dot com>
- To: Cygwin <cygwin at cygwin dot com>, Corinna Vinschen <corinna-cygwin at cygwin dot com>
- Date: Fri, 13 Nov 2009 15:15:21 -0800 (PST)
- Subject: Re: 1.7 file permissions changes
> Without more details I hazard a guess: The Windows process creates the
> directory without permissions for you to delete the directory or files
> in that directory and you're running under UAC.
Yes, this turns out to be true. I disabled UAC entirely and now my program works.
Is there a better way to share file and directory creation, modification and deletion between Cygwin processes and ordinary Windows processes, such that disabling UAC is not required? Some combination of umask and/or chmod on the Cygwin side with FileSetAttrib in Autoit (roughly equivalent to SetFileAttributes in the Windows API)? There is only one Windows user involved. As a Unix hacker I am somewhat mystified by this behavior.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple