115 .RE
 116 
 117 .sp
 118 .ne 2
 119 .na
 120 \fB\fBlog=tag\fR\fR
 121 .ad
 122 .sp .6
 123 .RS 4n
 124 Enables \fBNFS\fR server logging for the specified file system. The optional
 125 tag determines the location of the related log files. The \fBtag\fR is defined
 126 in \fBetc/nfs/nfslog.conf\fR. If no \fBtag\fR is specified, the default values
 127 associated with the \fBglobal\fR \fBtag\fR in \fBetc/nfs/nfslog.conf\fR is
 128 used. Support of NFS server logging is only available for NFS Version 2 and
 129 Version 3 requests.
 130 .RE
 131 
 132 .sp
 133 .ne 2
 134 .na

























 135 \fB\fBnone=\fR\fIaccess_list\fR\fR
 136 .ad
 137 .sp .6
 138 .RS 4n
 139 Access is not allowed to any client that matches the access list. The exception
 140 is when the access list is an asterisk (\fB*\fR), in which case \fBro\fR or
 141 \fBrw\fR can override \fBnone\fR.
 142 .RE
 143 
 144 .sp
 145 .ne 2
 146 .na
 147 \fB\fBnosub\fR\fR
 148 .ad
 149 .sp .6
 150 .RS 4n
 151 Prevents clients from mounting subdirectories of shared directories. For
 152 example, if \fB/export\fR is shared with the \fBnosub\fR option on server
 153 \fIfooey\fR then a \fBNFS\fR client cannot do:
 154 .sp

 115 .RE
 116 
 117 .sp
 118 .ne 2
 119 .na
 120 \fB\fBlog=tag\fR\fR
 121 .ad
 122 .sp .6
 123 .RS 4n
 124 Enables \fBNFS\fR server logging for the specified file system. The optional
 125 tag determines the location of the related log files. The \fBtag\fR is defined
 126 in \fBetc/nfs/nfslog.conf\fR. If no \fBtag\fR is specified, the default values
 127 associated with the \fBglobal\fR \fBtag\fR in \fBetc/nfs/nfslog.conf\fR is
 128 used. Support of NFS server logging is only available for NFS Version 2 and
 129 Version 3 requests.
 130 .RE
 131 
 132 .sp
 133 .ne 2
 134 .na
 135 \fB\fBnohide\fR\fR
 136 .ad
 137 .sp .6
 138 .RS 4n
 139 
 140 By default, if a server exports two filesystems, one of which is mounted as a
 141 child of the other, NFS Version 2 and Version 3 clients must mount both
 142 filesystems explicitly in order to access them. If a client only mounts
 143 the parent, it will see an empty directory at the location where the other
 144 filesystem is mounted.
 145 
 146 Setting the \fBnohide\fR option on a filesystem causes it to no longer be
 147 hidden in this manner, and a client will be able to move from the parent
 148 filesystem to this one without noticing the change. However, some NFS clients
 149 or applications may not function correctly when this option is used. In
 150 particular, files on different underlying filesystems may appear to have the
 151 same inode numbers.
 152 
 153 This option is equivalent to the option of the same name provided in \fBLinux
 154 NFS\fR, and only applies to NFS Version 2 and Version 3 requests.
 155 .RE
 156 
 157 .sp
 158 .ne 2
 159 .na
 160 \fB\fBnone=\fR\fIaccess_list\fR\fR
 161 .ad
 162 .sp .6
 163 .RS 4n
 164 Access is not allowed to any client that matches the access list. The exception
 165 is when the access list is an asterisk (\fB*\fR), in which case \fBro\fR or
 166 \fBrw\fR can override \fBnone\fR.
 167 .RE
 168 
 169 .sp
 170 .ne 2
 171 .na
 172 \fB\fBnosub\fR\fR
 173 .ad
 174 .sp .6
 175 .RS 4n
 176 Prevents clients from mounting subdirectories of shared directories. For
 177 example, if \fB/export\fR is shared with the \fBnosub\fR option on server
 178 \fIfooey\fR then a \fBNFS\fR client cannot do:
 179 .sp