On 01/06/2010 09:22 PM, Raman Gupta wrote:
I have an smbfs mount (served by samba 3.4.2) in noacl mode on cygwin
1.7.1-1:
//smserver/smshare on /mnt/shar type smbfs (binary,notexec,noacl,user)
Here is the directory as seen on the unix server directly:
r...@smserver foo]# ls -ald bar
dr-xr-sr-x. 2 root agroup 4096 2007-04-21 23:23 bar
As you can see, the directory bar is not writable.
However, here is what cygwin in noacl mode sees:
Raman gu...@client /mnt/shar/foo
$ ls -ald bar
drwxr-xr-x 1 Raman Gupta None 0 2007-04-21 23:23 bar
The mode shown is 755 rather than 555, and indeed cygwin does not have
write access to this directory:
Raman gu...@client /mnt/shar/foo/bar
$ touch baz
touch: cannot touch `baz': Permission denied
Shouldn't cygwin therefore read the permissions as 555?
In acl mode, cygwin does correctly show these directory permissions as 555.
Note that read-only *files* are correctly displayed by cygwin/noacl as 444.
Well, you've told Cygwin that it shouldn't consult the file system for
permissions.
So you see is what Cygwin defaults to in these situations. If you ask Cygwin
to tell you the permissions on something in a file system where you also told
it not to check the permissions, you don't expect to see the actual correct
permissions, do you?
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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
