cluster ignore the changes in the permission

Question

Hi I am reading the article Using mac os x client with isilon ones 6.5 the page 25 I like the option cluster ignore the changes in the permission I applied the recommendations Isilon OneFS v6.5.4.4 paco1-3# sysctl efs.bam.acl_policies efs.bam.acl_policies: 65796 paco1-3# perl -e 'printf '%d
', 65796 & ~0xc27 | 0x800 | 0x40000000 | 0x2;' 1073809666 paco1-3# isi_sysctl_cluster efs.bam.acl_policies=1073809666 Value set successfully i have a folder prueba1 with the permission before the commands: 775 drwxrwxr-x +  2 root  wheel    0 May 15 15:44 prueba1 after the commands the permission was: 777 drwxrwxrwx +  2 root  wheel    0 May 15 15:44 prueba1 I understood that if applied the commands the client can't modify the permission inside of isilon, the files always keep the permission but I applied the commands the permission changed from 775 to 777 the commands help to avoid the change in the permission by the client? could I put whatever permission or always be 777? What command do you recommend me to custom the permission? if i want to put 775 or 774 how to put the permissions? I am the laboratory cluster with the version onefs 6.5 macosx maverick mac osx 10.6.8 nfs protocol Thanks

mattashton1 · Answer

Hi Francisco,

The intent of the guide was to force a wide open environment where permissions are basically ignored, resulting in 777 regardless of what the clients set the permissions to. Previous steps included mapping all users and groups to nobody on the NFS exports and setting an inheritable ACL at the root of the share giving everyone access.

The commands you quoted above would result in the cluster ignoring any attempts by clients to change permissions and report back 777 if an ACL exists.

I am not sure what you are asking for later on, as at this point, the cluster and clients are ignoring any UID/GID and permissions are wide open. A more restrictive default POSIX mapping? That could be problematic if you are ignoring UID/GIDs.

Cheers,
Matt

Paconet1 · Answer

Thanks for your answer

When I applied the command automatically the cluster changed the permission to 777.

Is there some procedure or command to restrict the change permission of client, and not put the permission to 777?

knargi · Answer

Where did you issue the permissions change?  If you did it from the Isilon Command Line as the root user than yes the permissions on the files would change because root has that authority.  Have you tried to issue a chmod on a file from the OSX client?

Paconet1 · Answer

Hi Yes the client couldn't change the permission

Isilon

cluster ignore the changes in the permission

Was this post helpful?