Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 19 Aug 2005 20:25:00 +0000 From: Christopher Benson-Manica To: cygwin@cygwin.com Subject: Re: Permissions, again Message-ID: <20050819202459.GA23900@SDF.LONESTAR.ORG> References: <20050819194352.GA28538@SDF.LONESTAR.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-IsSubscribed: yes > chmod, and other POSIX programs know nothing about ACLs (which is where > inheritance is specified). You should, however, be able to use > "getfacl/setfacl" to do what you want. Hm... It seems that (get|set)facl do allow detailed permissions to be set, but what I really need is the inherited property/attribute/whatever to be set, as these files need to have permissions matching those of their final destinations. It's okay to tell me "Don't be absurd!" but I haven't heard it yet :-) Incidentally, while I was using the ntsec default for permissions, all this stuff worked correctly... Also, with umask set to 077, a file I create with "touch" will end up with NT permissions for read and write, but not execute, as well as numerous other types of permissions. -- Christopher Benson-Manica ataru(at)sdf.lonestar.org -- 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/