Lines Matching full:be
13 .\" may be used to endorse or promote products derived from this software
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
55 A long line may be split over several lines by ending all but the
58 A host may be specified only once for each local file system or the NFSv4 tree
59 root on the server and there may be only one default entry for each server
68 that can be mounted on by the corresponding client(s).
70 files below the exported directory will be accessible.
74 To provide this guarantee, the exported directories must be local file system
80 is not a file system mount point, then clients will be able to access arbitrary
82 As such, to avoid confusion with respect to what is exported, it may be prudent
100 This list of directory paths should be considered an
139 allowing special characters to be included in the directory name(s).
141 can be handled.
142 For example, a blank can be encoded as \(rs040.
146 option may be used to encode directory name(s) with embedded special
151 The second component of a line specifies how the file system is to be
156 For the NFSv4 tree root, the only options that can be specified in this
173 The user may be specified by name or number.
174 The user string may be quoted, or use backslash escaping.
180 to be used for remote access by root.
181 The elements of the list may be either names or numbers.
184 should be used to specify a credential containing no groups, in which case the
199 The group names may be quoted, or use backslash escaping.
216 in an effort to be backward compatible with older export file formats.
223 All other users will be mapped to their remote credential.
227 remote access by root will be mapped to that credential instead of 65534:65533.
231 all users (including root) will be mapped to that credential in
237 specifies a colon separated list of acceptable security flavors to be
240 If multiple flavors are listed, they should be ordered with the most
247 option specifies that the file system should be exported read-only
253 in an effort to be backward compatible with older export file formats.
263 is only provided to conform to the spec, and should normally not be used.
276 Note that only one file system can be
284 option can be used to specify a file whose handle will be returned if
290 option is specified, a directory filehandle will be returned as usual.
308 must be running on the server.
323 will be translated to the credentials of the specified user in the same
331 All RPCs will be performed using these credentials instead of the
345 This can be useful to avoid annoying error messages for known possible
351 The set may be specified in three ways.
355 addresses may be used in place of names.)
374 first and are assumed to be hostnames otherwise.
385 The netmask may be specified either by attaching a
413 There can only be one NFSv4 root directory per server.
416 this location can be any directory and does not
417 need to be within an exported file system.
421 Although parts of the NFSv4 tree can be non-exported, the entire NFSv4 tree
423 All ZFS file systems in the subtree below the NFSv4 tree root must be
431 option on these line(s) specifies what security flavors may be used for
444 utility can be made to re-read the
551 address must be complete, and not just contain the upper bits.
554 option must not be used.
558 will be exported read-only to the entire network 192.168.33.0/24, including
577 would normally be syslogged.
578 As soon as an actual CD-ROM is going to be mounted,
584 file system will be exported as intended.
596 will be exported using Kerberos 5 authentication and will require
600 will also be exported using Kerberos 5 authentication and all messages
601 used to access it will be encrypted.
673 must be non-contradictory for any exported subdirectory of the local
676 file system be specified on adjacent lines going down the tree.