Mark Rogers wrote:
I have a Samba share setup thus: [projects] path = /var/flexshare/shares/projects comment = Projects Drive create mask = 664 directory mask = 775 force group = user public = no valid users = @user browseable = yes writeable = yes
This has files written to it by a number of users on Windows, and myself from a Linux desktop. When the Windows users create files, they're group writable (ie any of us can modify them), but when I create them nobody else gets write access.
Sounds like the umask is getting in the way, or the Linux client is picking something up from the mount points permissions.
One reasonably evil way (assuming you don't mind not being able to set file permissions from the unix client end) is to add the following to the servers smb.conf file
unix extensions = no
Until a few years ago this was the default behavior for samba. Without this a umask from a unix host can override any creation masks you have in your samba configuration.
Wayne
I am accessing the share through a cifs mount, as follows: //10.0.0.14/projects /smb/projects cifs credentials=/smb/.credentials,dir_mode=0775,uid=1000,gid=1010 0 0
(word-wrap added for email).
Any ideas what is wrong?
Something to note is that all users exist on the file server, and if I look at the directory listings in the shares from the file server then files are all owned by <user>.user (eg mark.user) depending who created them (to be clear, the group name is "user", the user name is that who created the file). However, if I list /smb/projects from my local machine, then all files are shown as owned by me (mark.user) regardless of who created them. This isn't a problem in itself, I only mention it in case it is relevant.