[linux-cifs-client] Re: Unable to create new file on windows 2000

[Ian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I forgot to mention in my previous mail that the output from smbcacls is
the same whether full control is set on or off on the network share.

Ian wrote:

| The following output came from sbmcacls run against the root of the share
|
| REVISION:1
| OWNER:S-1-5-32-544
| GROUP:S-1-5-21-1713796142-668341455-4547331-512
| ACL:S-1-5-21-1713796142-668341455-4547331-512:0/3/0x001f01ff
| ACL:S-1-5-21-1713796142-668341455-4547331-4652:0/3/0x001301bf
|
| How do the acl settings differ when using smbfs as opposed to cifs? When
| I mount the same share using smbfs I do not see the same behaviour i.e.
| I can create new files without having to have full control over the share.
|
| The change in permissions is done to the network share rather than on
| the ntfs settings i.e. when using cifs we set full control on the
| network share whilst the ntfs acls deny full control.
|
| Cheers,
| Ian
|
|
| Steve French wrote:
|
| |What you describe is a little unusual but it does seem to be possible to
| |set Windows ACLs on the server side to behave as you describe.  To make
| |sure you have described the ACL on that directory exactly - could you
| |append the output of the Windows tool "cacls" run on that directory (or
| |the Samba utility "smbcacls" if it could be remotely against that UNC
| |name).   |
| |I do remember fixing a client bug (unique to 2.4 implementation of cifs
| |vfs, not present in the 2.6 version) that was temporarily introduced in
| |the file create path (when a 2.6 fix was backported) that for one
| |version of fs/cifs/file.c caused the wrong CIFS open flags to be set
| |(file creation in Linux is complicated since it is not an atomic
| |operation and at least in 2.4 involves about 8 distinct operations).
| |This bug is not present in the current cifs code, and is probably not
| |what you were running into.
| |
| |>~    I have access to read and modify existing files and create new
| |>directories under the root. However I get the following error when
| |>attempting to create a new file
| |>
| |>Status code returned 0xc0000022 NT_STATUS_ACCESS_DENIED
| |
| |
| |>~   If the security settings on the share are changed to allow full
| |>control then the create will work. Is this a server or client problem?
| |
| |
| |_______________________________________________
| |linux-cifs-client mailing list
| |linux-cifs-client at lists.samba.org
| |http://lists.samba.org/mailman/listinfo/linux-cifs-client


_______________________________________________
linux-cifs-client mailing list
linux-cifs-client at lists.samba.org
http://lists.samba.org/mailman/listinfo/linux-cifs-client
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAGjrVzR2KhuAWJ/gRAnprAKCLY7v1OaddGVPsFHifJmqJaBSgHACgij4S
FUa8or2sV6fPvRXFvHpHVKs=
=X21/
-----END PGP SIGNATURE-----