Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <43599AD7.EBB766FF@dessent.net> Date: Fri, 21 Oct 2005 18:50:15 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: BUG? mkdir ACLs References: <000001c5d6a2$a4d585b0$4105a8c0 AT JDNDEV> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Jeff Newmiller wrote: > ACLs for directories created with cygwin mkdir are significantly > different than ACLs for directories created by native methods. > In particular, the cygwin mkdir fails to include the > NT AUTHORITY\SYSTEM user ACL, preventing services from accessing > directories made this way. If this is by design, a FAQ should > be included warning of this and explaining why. The default umask is 0022 which means that any files created by the shell will be readable by all but only writable by the owner (0755 for directories) which is what you're seeing. That's how it works on unix, so that's how Cygwin does it. If you want something else, change the umask or use "nontsec". Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/