X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <501545.51925.qm@web65401.mail.ac4.yahoo.com> Date: Fri, 13 Nov 2009 15:15:21 -0800 (PST) From: Eric Benson Subject: Re: 1.7 file permissions changes To: Cygwin , Corinna Vinschen MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > 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 FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple