New OMV installation, everything looks and works good, but I can't write to the share

Zitat von JackElliott

drwxrwsrwx+ 12 root users 4096 Nov 27 13:06 BMP

You must change rws in the group to rwx to make the folder executable.

chown -R 775 /path/to/BMP

replace /path/to/ with the actual path to your BMP folder

You only need to change the owner if you want to grant different permissions to the owner than to the other users in the group.

- If you want all users in the users group to be able to read and write use 775, it is equivalent to read and write permissions for owner and users of the group. All other users can only read. In this case it does not matter who the owner is.

- If you want to grant the owner different permissions than the other users in the users group, for example 755, the owner can read and write and the other users in the group can only read. All other users can only read.

In this case the owner must change. You can do it with:

chown -R jack:users /path/to/BMP

chmod -R 755 /path/to/BMP

replace jack with your username

replace /path/to/ with your actual path to the BMP folder

Zitat von Zoki

group has +s (SGID) bit set, so

everybody in group users should be able to cd to BMP.
every file created in that directory should have group users

That's why I said in post No. 4 to change "s" to "x", this is so that the folder is accessible (executable) to the users of the group.

Zitat von Zoki

but the + in the files umask indicates, some ACLs are set.

You're right, I didn't notice this. This is the problem with using ACL permissions. Complicate things. The best thing would be to remove the ACL permissions, as you indicate. Unless the OP wants to define permissions for some users besides the owner and not for the rest of the group.

Personally, I only assign permissions by groups, never user. Root owns everything on my system, and groups are what restricts/allows users to certain directories. It's much easier IMO... even w/ only 2-3 users, it's just easier IMO.

I don't use SMB, but I can't imagine this would cause an issue.

A Group= r/w on everything

B Group= r/w on some things, r/o only on others.

C Group = r/o on everything.

Create a user, throw it in the appropriate group, voila.

Zitat von KM0201

Create a user, throw it in the appropriate group, voila.

In this case, the permissions of the shared folder of the OP are not set correctly. If this is not resolved, nothing will work.

Zitat von chente

In this case, the permissions of the shared folder of the OP are not set correctly. If this is not resolved, nothing will work.

I never suggested otherwise. You took one line from my post, which basically said how easy it was to assign permissions by group in my setup... and attempted to apply it to his situation.

Ok, this suggested general configuration confirms what has already been said earlier in this thread. Thanks.

Zitat von JackElliott

I don't need ACL.

As zoki said very well in post # 7, first check if your BMP folder has ACL permissions set.

getfacl /path/to/BMP

replace /path/to/ with your actual path to the BMP folder

If you have configured permissions you must delete them with:

setfacl -b -R /path/to/BMP

Important! Make sure of the route.

Zitat von JackElliott

I want any member of the group "users" to have rwx permisions on all files and folders.

Root can own everything, that's okay by me.

For this you can run:

chown -R root:users /path/to/BMP # This should not be necessary if you haven't modified anything since post # 3

chmod -R 775 /path/to/BMP

Zitat von Zoki

s is equal to x plus inherit group.

If the s is missing, everybody creates files with his primary group and they are not readable by others.

Zoki , you are a crack. Once again I have to agree with you. Thanks for your input.

I've never noticed this because I don't use groups for my users. I only used the users group. Therefore, I don't need it. But in case of using different groups it will be necessary to have this flag.

What this flag does is grant the current user the permissions of the owner user or group, depending on the position in which it is configured. This way, if the s flag is set on the group, when a file is created, it will be created with the group from the parent folder, not the user who is creating it.

The precaution is to configure it for the group, not for the user. If it is configured for the user and the owner is root, we would be granting the user at that moment root permissions. This allows in some cases access to root permissions.

In my case, as I said before, it is not necessary, but to use different groups the flag s should be used in the position of the group, this is done by placing a 2 before the definition of the permissions.

Therefore, the command to use would be in this case:

chmod -R 2775 /srv/dev-disk-by-uuid-1d4d5a04-39e8-4c30-8518-15271f3d1f43/BMP

Thanks for forcing me to study!