linux - Setting up ACL permission - creating new directory applies wrong filter (default problems) -
When I run down I get ACL settings below. The problem occurs when I make a new directory for some reason For the default ACL parameter new DIR
AppUser1 @ r01mgt: ~ $ hadoop fs -getfacl / somedir / # file: / somedir # The owner is not being passed: Owner # 1 group: Group 1 user :: rwx group :: rx group: group 2: rx group: group 3: arvwex mask :: rwx other :: Rx Default: User: RWX Default: Group :: Rx Default: Group: Group 2: Rx Default: Group: Group3: rwx Default: Mask :: RWX Default: Other :: RX - CREATE new dir AppUser1 @ r01mgt: ~ $ Hadoop fs-getfacl / somedir # file owner: owner # 1 group: group 1 user:: rwx group :: rx group: group 2: rx group: group 3: rwx # effect: rx mask: : RX Others :: Rx Default: User: RWX Default: Group :: Rx Default: Group: Group 2: Rx Default: Group: Group 3: RWX Default: Mask :: RWX Default: Other :: Rx
Does anyone know That's why my group: Group 3: RWX becomes effective RX? And why does my Mask R-X? Is this due to Umask?
see < ACL succession struggle with Em> umaskmode
... ADC value (user, Group and HDFS masks other than Possix owner)
dfs.umaskmode
with properties of the group mask when they make directories with ACL inherited ... This is a deviation from the posix ACL specs < / P>... make this change in a 2.x line in a consistent way backwards It is impossible ... if a customer upgrades ahead of the Nano ... neither the customer nor the NameNode Umask will apply ... which will definitely compromise security.
I have it 3.0.0 I'm targeting again.
Comments
Post a Comment