254 Posts

March 20th, 2015 14:00

Here are some tips:

First, you can clear out the current ACLs with the following:

chmod -D /ifs/share

I think that's easier than removing each one.

Then add back in any entries following this example:

chmod +a group domain\\group_name allow dir_gen_read,dir_gen_write,dir_gen_execute,std_delete,object_inherit,container_inherit /ifs/share

Notice the double \\, this helps the shell interpret the backslash properly. This should be on all one line, not sure if the editor here will allow that or not.  But assume it is.  So do that for each entry with the correct names and properties as appropriate.

Then for CONTROL properties, do the following:

chmod -c +dacl_auto_inherited /ifs/share

chmod -c +dacl_protected /ifs/share

So, in your case, it could be a series of chmod commands, but if it's scripted, it shouldn't be too bad.


It can be a bit confusing, but once you get used to it, it's not too bad.  The man page for chmod is very good at explaining what each of the settings mean as well as syntax.  You just have to pan down to the bottom where the Isilon-specific ACL settings are.


Hope this helps.

10 Posts

March 20th, 2015 18:00

Thanks Adam!

That's exactly what I was looking for.  I had opened the man page for chmod but didn't read far enough down to see the Isilon customizations.

I knew chmod was the answer and chmod +a was the first part of the command to add the permissions but I \was over thinking the syntax for the attributes.  Imaging that, something as simple as plain English.

10 Posts

March 24th, 2015 08:00

D'Alessandro or Verrico?

254 Posts

March 24th, 2015 08:00

Glad to hear it.

Say hi to Vinnie for me.

254 Posts

March 24th, 2015 12:00

Verrico. He's on of the SEs I support as a CAE.

10 Posts

March 24th, 2015 13:00

Will do.  Probably talking to him later this week.

No Events found!

Top