X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 21 Oct 2011 16:39:13 +0200
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: <20111021143913.GE2976@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CC0D9E8456BA41488A76AFE4E8F3A36902731CC0 AT de011305 DOT de DOT ina DOT com> <j7q925$5sd$1 AT dough DOT gmane DOT org> <20111021085010 DOT GF13505 AT calimero DOT vinschen DOT de> <CC0D9E8456BA41488A76AFE4E8F3A3690278A577 AT de011305 DOT de DOT ina DOT com> <20111021105510 DOT GC2979 AT calimero DOT vinschen DOT de> <j7rus9$e59$1 AT dough DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <j7rus9$e59$1@dough.gmane.org>
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 Oct 21 10:16, gds wrote:
> On 10/21/2011 06:55 AM, Corinna Vinschen wrote:
> >On Oct 21 12:15, Lemke, Michael  SZ/HZA-ZSW wrote:
> >>On Friday, October 21, 2011 10:50 AM
> >>Corinna Vinschen wrote:
> >>>
> >>>On Oct 20 18:58, gds wrote:
> >>>>On 10/18/2011 08:52 AM, Lemke, Michael SZ/HZA-ZSW wrote:
> >>>>
> >>>>>
> >>>>>I know this an old thread but I am in exactly the same situation as
> >>>>>the OP.  Access with 1.7.7 and before worked fine, 1.7.9 has this
> >>>>>problem.  The workaround with explicit noacl option works for me but
> >>>>>it is rather awkward as I have to work with a lot of servers.
> >>>>>
> >>>>>So...
> >>>>>
> >>>>
> >>>>>
> >>>>>...has this happened now?  In a snapshot?  I couldn't find any
> >>>>>further information.
> >>
> >>So from the reply below I take it hasn't been fixed/worked
> >>around in a snapshot.  But my experiments show something has
> >
> >Wrong.  It has been fixed in the snapshot.  1.7.9 tries to open the file
> >with WRITE_DAC access which fails on some shares.  The snapshots won't
> >do that anymore.
> >
> >>>I explained what the problem is already.  The buzzword is WRITE_DAC.
> >>>Apparently you don't have permissions to change file permissions
> >>>on that share.  Cacls should show the exact layout of the file and
> >>>directory DACLs.  Does `chmod' work for you?  It shouldn't either.
> >>
> >>In my case that it true, chmod fails.
> 
> For me chmod *appears* to work (no errors on cmd line) but file
> permissions seen in "ls -l" don't change nor do they change in
> windows.

This is *with* using the "noacl" mount option, isn't it?  Without
the "noacl" option you should get a "Permission denied" on chmod.

> Also, in
> windows, I can't change any of my access rights; under file
> properties/security under "allow" all are checked except Full
> Control and Special permissions, none checked under "Deny" and all
> check marks are gray so I can't change them there either. Anyone can
> create, modify or delete any file, but no one can hide or
> write-protect any file (which would require changing
> permission/access rights).
> 
> AFAIK, this is how it has always been on this share. If this
> assumption is correct, does that mean something changed in cygwin
> that is causing this possible bug?

I explained that in this thread.  WRITE_DAC vs. not WRITE_DAC.

> >Then "noacl' is the only way for you.
> 
> Yes, no snapshot cygwin1.dll helped. Went back to default. Now have
> only this in /etc/fstab:
> 
> O: /my-o-drive	dontcare binary,noacl 0 0
> 
> So now access drive with /my-o-drive instead of /cygdrive/o

Yes, that's how it's supposed to be in your situation.


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