LU-12885 llapi: use enum llapi_layout_get_flags

[fs/lustre-release.git] / lustre / doc / lctl-nodemap-modify.8

diff --git a/lustre/doc/lctl-nodemap-modify.8 b/lustre/doc/lctl-nodemap-modify.8
index 8e01dea..970cc56 100644 (file)
--- a/lustre/doc/lctl-nodemap-modify.8
+++ b/lustre/doc/lctl-nodemap-modify.8
@@ -1,7 +1,6 @@
-.TH lctl-nodemap-modify 8 "2015 Jan 20" Lustre "configuration utilities"
+.TH LCTL-NODEMAP_MODIFY 8 "2019-01-22" Lustre "configuration utilities"
 .SH NAME
-lctl-nodemap-modify \- Modify a nodemap property.
-
+lctl-nodemap_modify \- modify a nodemap property
 .SH SYNOPSIS
 .br
 .B lctl nodemap_modify <--name nodemap_name> <--property property_name>
@@ -42,6 +41,27 @@ squash_gid
 .RS 4
 Defaults to 99. The group ID that unknown groups (if not trusted) and root (if not admin) should be mapped to.
 .RE
+.PP
+deny_unknown
+.RS 4
+Defaults to off. If set to on then unknown (squashed) users will be denied
+access to the filesystem completely instead of just being squashed. Users are
+considered unknown by nodemap if the admin flag is off and the user is root, or
+trusted are set to off and the user is not mapped.
+
+Note: directory entries cached by a Lustre client may be visible to unknown
+users located on the same client, though the contents of the files will not be.
+.RE
+.PP
+audit_mode
+.RS 4
+Defaults to on, which lets clients record file system access events to the
+Changelogs, if Changelogs are otherwise activated. If set to 0, events from
+these clients are not logged into the Changelogs, no matter if Changelogs are
+activated or not.
+The reason not to record file system events from given clients is to prevent
+some nodes (e.g. backup, HSM agent nodes) from flooding the Changelogs.
+.RE
 
 .I value
 is the value to set for the property. Should be 0 or 1 for admin and trusted.