155 Load
 156 .Ar file
 157 rather than a listing of the directory containing this file when the
 158 directory is referenced by an NFS URL.
 159 .It Sy log Ns Oo = Ns Ar tag Oc
 160 Enables NFS server logging for the specified file system.
 161 The optional
 162 .Ar tag
 163 determines the location of the related log files.
 164 The
 165 .Ar tag
 166 is defined in
 167 .Pa /etc/nfs/nfslog.conf .
 168 If no
 169 .Ar tag
 170 is specified, the default values associated with the global tag in
 171 .Pa /etc/nfs/nfslog.conf
 172 are used.
 173 Support of NFS server logging is only available for NFS Version 2 and
 174 Version 3 requests.



















 175 .It Sy noaclfab
 176 By default, the NFS server will fabricate POSIX-draft style ACLs in response
 177 to ACL requests from NFS Version 2 or Version 3 clients accessing shared
 178 file systems that do not support POSIX-draft ACLs (such as ZFS).
 179 Specifying
 180 .Sy noaclfab
 181 disables this behavior.
 182 .It Sy none Ns = Ns Ar access_list
 183 Access is not allowed to any client that matches the access list.
 184 The exception is when the access list is an asterisk (*), in which case
 185 .Sy ro
 186 or
 187 .Sy rw
 188 can override
 189 .Sy none .
 190 .It Sy nosub
 191 Prevents clients from mounting subdirectories of shared directories.
 192 For example, if
 193 .Pa /export
 194 is shared with the

 769 .Xr mountd 1M
 770 process allows the processing of a path name that contains a symbolic link.
 771 This allows the processing of paths that are not themselves explicitly shared
 772 with
 773 .Nm .
 774 For example,
 775 .Pa /export/foo
 776 might be a symbolic link that refers to
 777 .Pa /export/bar
 778 which has been specifically shared.
 779 When the client mounts
 780 .Pa /export/foo
 781 the mountd processing follows the symbolic link and responds with the
 782 .Pa /export/bar .
 783 The NFS Version 4 protocol does not use the mountd processing and the client's
 784 use of
 785 .Pa /export/foo
 786 does not work as it does with NFS Version 2 and Version 3 and the client
 787 receives an error when attempting to mount
 788 .Pa /export/foo .

 155 Load
 156 .Ar file
 157 rather than a listing of the directory containing this file when the
 158 directory is referenced by an NFS URL.
 159 .It Sy log Ns Oo = Ns Ar tag Oc
 160 Enables NFS server logging for the specified file system.
 161 The optional
 162 .Ar tag
 163 determines the location of the related log files.
 164 The
 165 .Ar tag
 166 is defined in
 167 .Pa /etc/nfs/nfslog.conf .
 168 If no
 169 .Ar tag
 170 is specified, the default values associated with the global tag in
 171 .Pa /etc/nfs/nfslog.conf
 172 are used.
 173 Support of NFS server logging is only available for NFS Version 2 and
 174 Version 3 requests.
 175 .It Sy nohide
 176 By default, if server exports two filesystems, one of which is mounted as a
 177 child of the other, NFS Version 2 and Version 3 clients must mount both
 178 filesystems explicitly in order to access them.
 179 If a client only mounts the parent, it will see an empty directory at the
 180 location where the other filesystem is mounted.
 181 .Pp
 182 Setting the
 183 .Sy nohide
 184 option on a filesystem causes it to no longer be hidden in this manner, and the
 185 client will be able to move from the parent filesystem to this one without
 186 noticing the change.
 187 However, some NFS clients or applications may not function correctly when
 188 this option is used.
 189 In particular, files on different underlying filesystems may appear to have
 190 the same inode numbers.
 191 The
 192 .Sy nohide
 193 option only applies to NFS Version 2 and Version 3 requests.
 194 .It Sy noaclfab
 195 By default, the NFS server will fabricate POSIX-draft style ACLs in response
 196 to ACL requests from NFS Version 2 or Version 3 clients accessing shared
 197 file systems that do not support POSIX-draft ACLs (such as ZFS).
 198 Specifying
 199 .Sy noaclfab
 200 disables this behavior.
 201 .It Sy none Ns = Ns Ar access_list
 202 Access is not allowed to any client that matches the access list.
 203 The exception is when the access list is an asterisk (*), in which case
 204 .Sy ro
 205 or
 206 .Sy rw
 207 can override
 208 .Sy none .
 209 .It Sy nosub
 210 Prevents clients from mounting subdirectories of shared directories.
 211 For example, if
 212 .Pa /export
 213 is shared with the

 788 .Xr mountd 1M
 789 process allows the processing of a path name that contains a symbolic link.
 790 This allows the processing of paths that are not themselves explicitly shared
 791 with
 792 .Nm .
 793 For example,
 794 .Pa /export/foo
 795 might be a symbolic link that refers to
 796 .Pa /export/bar
 797 which has been specifically shared.
 798 When the client mounts
 799 .Pa /export/foo
 800 the mountd processing follows the symbolic link and responds with the
 801 .Pa /export/bar .
 802 The NFS Version 4 protocol does not use the mountd processing and the client's
 803 use of
 804 .Pa /export/foo
 805 does not work as it does with NFS Version 2 and Version 3 and the client
 806 receives an error when attempting to mount
 807 .Pa /export/foo .
 808 .Pp
 809 The
 810 .Sy nohide
 811 option violates RFC 1094,
 812 .%T "Network File System Protocol Specification"
 813 and RFC 1813,
 814 .%T "NFS: Network File System Version 3 Protocol Specification"
 815 .Pp
 816 The
 817 .Sy nohide
 818 option is provided for compatibility with Linux NFS.