X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject:	Use of acl on smb related filesystems
Date:	Mon, 23 Jan 2012 17:38:37 -0800
Lines:	49
Message-ID:	<jfl22v$1cr$1@dough.gmane.org>
Mime-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

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 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. 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 but 
that doesn't seem to be working.

Where am I reading this incorrectly?
-- 
Andrew DeFaria <http://defaria.com>
For people who like peace and quiet: a phoneless cord.


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

- Raw text -