We are using a share by two users: mni:*:15005:10000:Manfred Nimtz:/home/mni:/bin/csh ufe:x:1163:10000:Undine Felgentraeger:/home/ufe:/bin/sh Both connect to this share from XP: [mni] comment = Home von Manfred Nimtz path = /home/mni browseable = yes writeable = yes create mask = 0660 directory mask = 0770 force create mode = 660 force directory mode = 770 follow symlinks = no ufe create a dir with dirs and files in it. They get: -rw-rw---- 1 ufe zib 7052 14. Aug 09:07 acqu -rw-rw---- 1 ufe zib 7052 14. Aug 09:07 acqus -rw-rw---- 1 ufe zib 32251 14. Aug 09:07 Analysis.FAmethod -rw-rw---- 1 ufe zib 474 14. Aug 09:07 AnalysisParameter.xml -rw-rw---- 1 ufe zib 476000 14. Aug 09:07 fid drwxrwx--- 3 ufe zib 4096 20. Aug 13:11 pdata/ -rw-rw---- 1 ufe zib 3 14. Aug 09:07 sptype ufe sees in XP: my files, read and write mni sees in XP: her files, READONLY. so mni cannot move this tree to another location, as he cannot remove the tree
Is "mni" member of the group "zib"?
I forgot: both are in the group zib: /etc/group zib:*:10000:...,nmi,...,ufe That is there login group.
I just upgraded to # smbclient -V Version 3.2.2-0.1.127-1874-SUSE-SL11.0 and checked my own account: Directories seems allway to be (partly) readonly. Why? I created a copy of a directory tree, changed owner, group write and all is o.k. Now go to PC 1, user ufe connect to mni create a dir "test" and subdirs and put files in them all. This is done by measuring SW on this PC or by copying the whole tree. On Linux I see the same as in #1. Go to PC 2, user mni try to remove test failed, cannot remove ANY file. Solution: temporally: GO to the linux box and: find . -type d -exec chmod o+w {} \; AND set directory mask = 0772 force directory mode =0772 find . -type d -exec chmod o+w {} \;
Jeremy, could you have a look at this one, please? Thanks!
What are the permissions on the containing directory /home/mni ? The permissions on the containing directory are what counts when deleting/moving files. If you want the permissions on the files to count you have to set "dos filemode = true". Jeremy.
I' just tried to reproduce the bug, as "something" changed during one year :-; At the moment I cannot reproduce it any more! Maybe the bug was related to somethin like bug 2009 We are now at: smbclient -V Version 3.2.7-0.1.135-2042-SUSE-SL11.0 (created 5.Jan 2009) But I'll have to test a little bit more befor closing.