X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 9 Jan 2012 14:50:59 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin permissions problem on a network drive
Message-ID: <20120109135059.GJ15470@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <alpine DOT WNT DOT 2 DOT 00 DOT 1201041506510 DOT 5432 AT CH01WW6077 DOT corp DOT ads>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <alpine.WNT.2.00.1201041506510.5432@CH01WW6077.corp.ads>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Jan  4 15:25, Markus Leuthold wrote:
> On Jul  5 10:59, Corinna Vinschen wrote:
> >On Jul  5 12:21, Bill Metzenthen wrote:
> >> What should I ask the system administrator to change so that cygwin
> >> will once again work on this drive? Perhaps there is some new setting
> >> (or an old one which has somehow changed) for cygwin that I have
> >> failed to notice?
> >
> >If you want to discuss this with your admin, the problem is this:  When
> >Cygwin 1.7.9 tries to create a file on a filesystem which supports ACLs,
> >it requests WRITE_DAC permissions in the open call.  WRITE_DAC is the
> >access right you need to create the permission bits in the file's ACL,
> >what you see in Explorer under the Security tab.
> >
> >Now, in some environments, the settings of the shares are so, that this
> >right is apparently not granted, even for the creator of the file.
> >But, as far as earlier reports go, there seem to be no indication of
> >this in the ACL.  As I mentioned above, I experimented with this
> >myself, but I have never managed to reproduce this setting on the
> server.
> >So I neither know how this setting looks like, nor if there's a way
> >to recognize such a share.
> >
> >Btw, if you're going to discuss this with your admin, and if you figure
> >out what server setting is the culprit, I would be glad if you could
> >share the information with us.  It might be a great help in developing
> >Cygwin further.
> >
> >
> >Thanks,
> >Corinna
> 
> 
> Hello Corinna
> 
> I've run into the same problem on a DFS filesystem, and I asked our
> admins about the settings. Please find a screenshot here:
> http://titlis.org/serversettings.png
> 
> The reason why "change permission" (=WRITE_DAC) was disabled: Our
> admins don't want to allow "take ownership" to everybody, since in
> the past users managed to set the rights such that even the admins
> couldn't access the file anymore. Since "take ownership"
> automatically enables "change permissions", WRITE_DAC is thus
> disabled too.
> 
> hope that helps

Thanks for the info.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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