X-Git-Url: https://git.whamcloud.com/?a=blobdiff_plain;f=ManagingSecurity.xml;h=64798b8998172bdbc7f5cbb40bca386d7a89ddcb;hb=0f3e4041a827c924fc95ab3a6f82298c46fbc970;hp=1f9a9b2ffba046e8cced77f30b99c1b629b473c1;hpb=b7dbb21244d38f3de56233079c04bed7ea29cb2e;p=doc%2Fmanual.git diff --git a/ManagingSecurity.xml b/ManagingSecurity.xml index 1f9a9b2..64798b8 100644 --- a/ManagingSecurity.xml +++ b/ManagingSecurity.xml @@ -54,7 +54,7 @@ To mount the client with no ACLs: $ mount -t lustre -o noacl ibmds2@o2ib:/home /home - ACLs are enabled in Lustre on a system-wide basis; either all clients enable ACLs or none do. Activating ACLs is controlled by MDS mount options acl / noacl (enable/disableACLs). Client-side mount options acl/noacl are ignored. You do not need to change the client configuration, and the “acl†string will not appear in the client /etc/mtab. The client acl mount option is no longer needed. If a client is mounted with that option, then this message appears in the MDS syslog: + ACLs are enabled in Lustre on a system-wide basis; either all clients enable ACLs or none do. Activating ACLs is controlled by MDS mount options acl / noacl (enable/disableACLs). Client-side mount options acl/noacl are ignored. You do not need to change the client configuration, and the 'acl' string will not appear in the client /etc/mtab. The client acl mount option is no longer needed. If a client is mounted with that option, then this message appears in the MDS syslog: ...MDS requires ACL support but client does not The message is harmless but indicates a configuration issue, which should be corrected. @@ -148,7 +148,7 @@ <anchor xml:id="dbdoclet.50438221_pgfId-1293871" xreflabel=""/>22.2.3 Tips on Using <anchor xml:id="dbdoclet.50438221_marker-1296366" xreflabel=""/>Root Squash Lustre configuration management limits root squash in several ways. - The lctl conf_param value overwrites the parameter’s previous value. If the new value uses an incorrect syntax, then the system continues with the old parameters and the previously-correct value is lost on remount. That is, be careful doing root squash tuning. + The lctl conf_param value overwrites the parameter's previous value. If the new value uses an incorrect syntax, then the system continues with the old parameters and the previously-correct value is lost on remount. That is, be careful doing root squash tuning.