83 The gidmap= option is evaluated before the anon=
84 option.
85
86 This option is supported only for AUTH_SYS.
87
88 index=file
89 Load file rather than a listing of the directory
90 containing this file when the directory is referenced
91 by an NFS URL.
92
93 log[=tag]
94 Enables NFS server logging for the specified file
95 system. The optional tag determines the location of
96 the related log files. The tag is defined in
97 /etc/nfs/nfslog.conf. If no tag is specified, the
98 default values associated with the global tag in
99 /etc/nfs/nfslog.conf are used. Support of NFS server
100 logging is only available for NFS Version 2 and
101 Version 3 requests.
102
103 noaclfab By default, the NFS server will fabricate POSIX-draft
104 style ACLs in response to ACL requests from NFS
105 Version 2 or Version 3 clients accessing shared file
106 systems that do not support POSIX-draft ACLs (such as
107 ZFS). Specifying noaclfab disables this behavior.
108
109 none=access_list
110 Access is not allowed to any client that matches the
111 access list. The exception is when the access list
112 is an asterisk (*), in which case ro or rw can
113 override none.
114
115 nosub Prevents clients from mounting subdirectories of
116 shared directories. For example, if /export is
117 shared with the nosub option on server "fooey" then a
118 NFS client cannot do:
119
120 mount -F nfs fooey:/export/home/mnt
121
122 NFS Version 4 does not use the MOUNT protocol. The
453
454 An NFS mount of server:/export/foo results in server:/export/bar really
455 being mounted.
456
457 This line in the /etc/dfs/dfstab file shares the /disk file system read-
458 only at boot time:
459
460 share -F nfs -o ro /disk
461
462 The mountd(1M) process allows the processing of a path name that contains
463 a symbolic link. This allows the processing of paths that are not
464 themselves explicitly shared with share_nfs. For example, /export/foo
465 might be a symbolic link that refers to /export/bar which has been
466 specifically shared. When the client mounts /export/foo the mountd
467 processing follows the symbolic link and responds with the /export/bar.
468 The NFS Version 4 protocol does not use the mountd processing and the
469 client's use of /export/foo does not work as it does with NFS Version 2
470 and Version 3 and the client receives an error when attempting to mount
471 /export/foo.
472
473 illumos March 23, 2017 illumos
|
83 The gidmap= option is evaluated before the anon=
84 option.
85
86 This option is supported only for AUTH_SYS.
87
88 index=file
89 Load file rather than a listing of the directory
90 containing this file when the directory is referenced
91 by an NFS URL.
92
93 log[=tag]
94 Enables NFS server logging for the specified file
95 system. The optional tag determines the location of
96 the related log files. The tag is defined in
97 /etc/nfs/nfslog.conf. If no tag is specified, the
98 default values associated with the global tag in
99 /etc/nfs/nfslog.conf are used. Support of NFS server
100 logging is only available for NFS Version 2 and
101 Version 3 requests.
102
103 nohide By default, if server exports two filesystems, one of
104 which is mounted as a child of the other, NFS Version
105 2 and Version 3 clients must mount both filesystems
106 explicitly in order to access them. If a client only
107 mounts the parent, it will see an empty directory at
108 the location where the other filesystem is mounted.
109
110 Setting the nohide option on a filesystem causes it
111 to no longer be hidden in this manner, and the client
112 will be able to move from the parent filesystem to
113 this one without noticing the change. However, some
114 NFS clients or applications may not function
115 correctly when this option is used. In particular,
116 files on different underlying filesystems may appear
117 to have the same inode numbers. The nohide option
118 only applies to NFS Version 2 and Version 3 requests.
119
120 noaclfab By default, the NFS server will fabricate POSIX-draft
121 style ACLs in response to ACL requests from NFS
122 Version 2 or Version 3 clients accessing shared file
123 systems that do not support POSIX-draft ACLs (such as
124 ZFS). Specifying noaclfab disables this behavior.
125
126 none=access_list
127 Access is not allowed to any client that matches the
128 access list. The exception is when the access list
129 is an asterisk (*), in which case ro or rw can
130 override none.
131
132 nosub Prevents clients from mounting subdirectories of
133 shared directories. For example, if /export is
134 shared with the nosub option on server "fooey" then a
135 NFS client cannot do:
136
137 mount -F nfs fooey:/export/home/mnt
138
139 NFS Version 4 does not use the MOUNT protocol. The
470
471 An NFS mount of server:/export/foo results in server:/export/bar really
472 being mounted.
473
474 This line in the /etc/dfs/dfstab file shares the /disk file system read-
475 only at boot time:
476
477 share -F nfs -o ro /disk
478
479 The mountd(1M) process allows the processing of a path name that contains
480 a symbolic link. This allows the processing of paths that are not
481 themselves explicitly shared with share_nfs. For example, /export/foo
482 might be a symbolic link that refers to /export/bar which has been
483 specifically shared. When the client mounts /export/foo the mountd
484 processing follows the symbolic link and responds with the /export/bar.
485 The NFS Version 4 protocol does not use the mountd processing and the
486 client's use of /export/foo does not work as it does with NFS Version 2
487 and Version 3 and the client receives an error when attempting to mount
488 /export/foo.
489
490 The nohide option violates RFC 1094, Network File System Protocol
491 Specification and RFC 1813, NFS: Network File System Version 3 Protocol
492 Specification
493
494 The nohide option is provided for compatibility with Linux NFS.
495
496 illumos March 23, 2017 illumos
|