understands the following export options:
.TP
.IR secure "\*d
-This option requires that requests originate on an internet port less
+This option requires that requests originate on an Internet port less
than IPPORT_RESERVED (1024). This option is on by default. To turn it
off, specify
.IR insecure .
.IR async
above).
-In releases of nfs-utils upto and including 1.0.0, this option was the
-default. In this and future releases,
+In releases of nfs-utils up to and including 1.0.0, this option was the
+default. In all subsequence releases,
.I sync
is the default, and
.I async
must be explicit requested if needed.
-To help make system adminstrators aware of this change, 'exportfs'
+To help make system administrators aware of this change, 'exportfs'
will issue a warning if neither
.I sync
nor
requested with
.IR subtree_check .
+From release 1.1.0 of nfs-utils onwards, the default will be
+.I no_subtree_check
+as subtree_checking tends to cause more problems than it is worth.
+If you genuinely require subtree checking, you should explicitly put
+that option in the
+.B exports
+file. If you put neither option,
+.I exportfs
+will warn you that the change is pending.
+
.TP
.IR insecure_locks
.TP
If a path is given (e.g.
.IR mountpoint= "/path or " mp= /path)
-then the nominted path must be a mountpoint for the exportpoint to be
+then the nominated path must be a mountpoint for the exportpoint to be
exported.
.TP