X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 24 Jan 2012 10:47:39 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Use of acl on smb related filesystems
Message-ID: <20120124094739.GI2456@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <jfl22v$1cr$1 AT dough DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <jfl22v$1cr$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 Jan 23 17:38, Andrew DeFaria wrote:
> OK I'm starting a new thread here for this different problem. Here's
> a problem statement:
> 
> Ltsdo-adefaria:pwd
> /home/adefaria
> Ltsdo-adefaria:mount | grep adefaria
> //fs-irva-82/adefaria on /home/adefaria type netapp (binary,user)
> Ltsdo-adefaria:touch foo
> Ltsdo-adefaria:ls -l foo
> -rw-r--r-- 1 adefaria clearusers 0 Jan 23 17:30 foo
> Ltsdo-adefaria:chmod 400 foo
> Ltsdo-adefaria:ls -l foo
> -r--r--r-- 1 adefaria clearusers 0 Jan 23 17:30 foo
> Ltsdo-adefaria:grep adefaria /etc/fstab
> //fs-irva-82/adefaria           /home/adefaria  ntfs
> binary,posix=1,user,acl 0 0
> Ltsdo-adefaria:
> 
> I've read through
> http://cygwin.com/cygwin-ug-net/using.html#mount-table and it's a
> little confusing to me. The part about acl says "Cygwin uses the
> filesystem's access control lists (ACLs) to implement real POSIX
> permissions (default).  This flag only affects filesystems
> supporting ACLs (NTFS) and is ignored otherwise". This seems to
> indicate that acl will only work on NTFS but it's not clear. Further

NTFS is just an example.  I change the wording.

> there are two examples of acl further down the page:
> 
> A mount point for a remote directory without ACL support:
> 
>   //server/share/subdir /srv/subdir smbfs binary,noacl 0 0
> 
> Seems odd to specify noacl if acls are not supported anyway.

Sigh.  Without ACL support by Cygwin.  Rephrased.

> And the
> example:
> 
>   //server/share /mysrv    ntfs     posix=1,acl   0 0
>   none           /cygdrive cygdrive posix=0,noacl 0 0
> 
> Assume there's a file \\server\share\foo on the share. When
> accessing it as /mysrv/foo, then the flags posix=1,acl of the /mysrv
> mount point are used. When accessing it as //server/share/foo, then
> the flags for the cygdrive prefix, posix=0,noacl are used.
> 
> Which seems to suggest that acl will be paid attention too if I
> access foo through /home/adefaria but not through
> //fs-irva-82/adefaria 

Exactly.

> but that doesn't seem to be working.

It's probably because your FS doesn't support ACLs.  Your mount
output

  //fs-irva-82/adefaria on /home/adefaria type netapp (binary,user)

shows that the path points to a NetApp drive.  NetApp drives have
various modes.  They can behave like FAT, NTFS, or a POSIX filesystem.
From your other report I assume it's set up not to support ACLs.
What does 

  $ /usr/lib/csih/getVolInfo //fs-irva-82/adefaria

print?


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