X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Subject: RE: cygwin permissions problem on a network drive Date: Fri, 21 Oct 2011 17:10:24 +0200 Message-ID: In-Reply-To: <20111021143621.GD2976@calimero.vinschen.de> References: <20111021085010.GF13505@calimero.vinschen.de> <20111021105510.GC2979@calimero.vinschen.de> <20111021143621.GD2976@calimero.vinschen.de> From: "Lemke, Michael SZ/HZA-ZSW" To: X-SEF-7853D99-ADF1-478E-8894-213D316B8FFA: 1 X-SEF-Processed: 7_3_0_01170__2011_10_21_17_10_24 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id p9LFB8Nm032379 On October 21, 2011 4:36 PM Corinna Vinschen wrote: >On Oct 21 16:13, Lemke, Michael SZ/HZA-ZSW wrote: >> On October 21, 2011 12:55 PM Corinna Vinschen wrote: >> >On Oct 21 12:15, Lemke, Michael SZ/HZA-ZSW wrote: >> >> This is by design here. IT wants it that way. >> > >> >Then "noacl' is the only way for you. >> >> Unless I wait for the next release, right? > >No. If you don't want to get a "Permission denied" error messages every >time some application tries to change the permissions, you will have to >use "noacl". It seems you don't understand what "acl" vs. "noacl" is >for. Does reading the User's Guide at >http://cygwin.com/cygwin-ug-net/using.html#mount-table help? No, that's not my problem. I am fine with the error message, it's correct after all. The real problem with 1.7.9 is that I can't create files although the permissions allow me to. And that seems to be fixed. > >> >Check with your admin and ask how they make sure that you can't set >> >permissions. Did they just create a certain set of inheritable >> >permissions or do they use some policy? That is what I'd like to know. >> >> I don't have a definitive answer yet but it looks like it's a >> policy. In Windows Explorer I have Full Access for the top level >> dir. That is inherited by every subdir and files. But the security >> entry is greyed out, also for subdirs. > >Ok, so there is some sort of policy. It would be nice to get some >"how to set up a share policy which doesn't allow changing permissions > for dummies" :) I'll see if I can get more from our admins. Michael