I have a rather simple question, for my Samba server I have a usergroup that everybody that I have that falls into that group has full Read Write, Execute permission. To the shared drive however instead of running chmod -R every time I update Samba when files or directories structures get changed that the permissions stay the same.
One recommend under the Parent Shared Directory Under Advance Permissions to enable or check off the sticky radio button. Please keep in mind I’m not running Samba in a LDAP Model more as a centralized storage model.
Or is there something in Samba I can adjust? what I’m getting is write permissions errors I can create new file or copy them however I can not delete them?
So I don’t have an answer for you since I don’t know what kind of partitions you are sharing and if you are using Samba because you have a mix of Windows and Linux machines. I use Samba because I want to allow file shares with Windows machines. As such, I have chosen to only share Windows NTFS partitions with Windows computers. On the Linux PC I have setup the fstab file so that the options for permissions and such have been reduced to just the single entry of defaults. The result for me is no worries with the ability to write or problems from Windows machines that do the writing. This may set you agast with terror, I am not sure, but it works for me. I would guess that a copy of your smb.conf file from the Linux computer(s) and a copy of at least one fstab file would be in order, to see what might be going on. Before you bear your soul to us here, one of our openSUSE forum users (swerdna) has a SUPER web site with lots of information about setting up Samba. I suggest you might want to look at this information.
Suselizard32, there are several solutions. But your exact problem is not clear to me. I think you have a situation where ppl on your LAN can log onto the central server and all share files with equal access and write permissions, and that they also have been made Linux users on the central server so that you can LAN login access for them using the “smbpasswd” function.
Share #5 - Basic secure read-write share. All users can edit and delete all items. Objects added to Share #5 will have the username & group of the creating user. A mix of owners will ensue on the Linux machine although it will not appear that way in a client network browser. Also, note that any file or directory can be deleted by any user, regardless of true ownership.
Share #8 - imposing uniform ownership with the force user parameter. This is tidier that share #5 because all objects assume a single central ownership regardless of the creator’s username.
And if you want to tighten security even more, and if your users all belong to a single group that you defined specially to contain only them, e.g. rascals, you can add this line into the [stanza] that you use for the shared directory, works for both #5 and #8 above: