I am at Samba 2.2.4 on Solaris 8 using Win2000 clients. The system default umask is 022 in /etc/profile and I have set user umask to 002 in .profile. Does Samba read/interpret either of these? All other setting are default but I have set global permissions to; create mask = 0664 force create mode = 0664 directory mask = 0775 force directory mode = 0775 and 'read = no' on the specific shares. It appears I am not getting the correct permissions. A newly created directory will have 777 in one share and 775 in another. A newly created file will have 777 in one share and 664 in another. I cannot find any consistency in setting these permissions. I have also se those parameter on specific share with the same result. I understand that 'create mask' is a ADD while 'force create mode' is an OR in setting permissions but it doesn't appear to be doing this, at least not consistently. At one point I thought it was ignoring Samba and UNIX and only getting permissions from the parent directory but this isn't the case in the above example. I log in/out of client for each test. What is going on? Is this a problem with my install or with V2.2.4? Any help would be appreciated. - Graeme
Well, I thought I knew Samba permissions, but I guess I don't. Currently, any user that has an account on the Samba server has access to the share "Accounting". So, let's say I have user1, user2, user3, user4 I have added user1, user2 and user3 to the accounting group. user4 is not a member of accounting. On the server itself (not for Samba), I set up permissions for the folder as 774 for all directories and files therein. User/group permission are set as admin.accounting The samba section for this share reads: [Accounting] comment = Accounting path = /home/accounting read only = No create mask = 0770 force create mode = 0770 security mask = 0770 directory mask = 0770 force directory mode = 0770 directory security mask = 0770 inherit permissions = Yes If any local user access this share, they also automatically become part of the accounting group (as far as samba is concerned). Now, if I add a line "valid users = user1, user2, user 3" then of course, just they can get in. But that doesn't seem to be the right solution. The right solution would be to permit only accounting group users into the folder. What am I doing wrong? -- Curtis Vaughan North Pacific Corporation http://www.angelfire.com/wa/noentry/home.htm WashTech (CWA Local 37083) IWW x353203
hi all im having some problems with my samba pdc , how would i go and create a group or user with permissions equevalent to "power users" in a windows enviornment At the moment they have restricted access and cant run certain programs The windows 2k workstations are being used by different users everyday so to give each user rights locally is not an option. kind regards ryan
I just installed samba on my private home network. It looks like I only have read access to shares. Using swat, I changed the create, security, and directory mask to 777, and committed the changes. But I still can't write. Can someone tell me what I did wrong?
Buck Turgidson napsal(a):> I just installed samba on my private home network. It looks like I only have > read access to shares. Using swat, I changed the create, security, and > directory mask to 777, and committed the changes. But I still can't write. Can > someone tell me what I did wrong? > >Commit itself only change config, but samba itself do not know about the change yet. Configs are automatically reread each 60 seconds (I think) otherwise you have to issue manual samba reload (in Debian invoke.rc samba reload). Are you sure that filesystem perms are ok? If everything look ok, run smbcontrol smbd debug 3 to rise amount of debug info and look into logs. Dan
On Sat, 25 Oct 2003, Buck Turgidson wrote:> I just installed samba on my private home network. It looks like I only have > read access to shares. Using swat, I changed the create, security, and > directory mask to 777, and committed the changes. But I still can't write. Can > someone tell me what I did wrong?Did you set in you share definition?: read only = No Did you add a password to the Samba encrypted password database using smbpasswd? ie: smbpasswd -a 'username' Did you set "log level = 5" and then ceck the log file to see why you are being disallowed from writing? - John T. -- John H Terpstra Email: jht@samba.org