|Linux & Unix Commands - Search Man Pages
EXPORTS(5) BSD File Formats Manual EXPORTS(5)
exports -- define remote mount points for NFS mount requests
The exports file specifies remote mount points for the NFS mount protocol per the NFS server
specification; see Network File System Protocol Specification RFC 1094, Appendix A and NFS:
Network File System Version 3 Specification, Appendix I.
Each line in the file (other than comment lines that begin with a #) specifies the mount
point(s) and export flags within one local server filesystem for one or more hosts. A host
may be specified only once for each local filesystem on the server and there may be only one
default entry for each server filesystem that applies to all other hosts. The latter
exports the filesystem to the ``world'' and should be used only when the filesystem contains
In a mount entry, the first field(s) specify the directory path(s) within a server filesys-
tem that can be mounted on by the corresponding client(s). There are two forms of this
specification. The first is to list all mount points as absolute directory paths separated
by whitespace. The second is to specify the pathname of the root of the filesystem followed
by the -alldirs flag; this form allows the host(s) to mount at any point within the filesys-
tem, including regular files if the -r option is used on mountd. The pathnames must not
have any symbolic links in them and should not have any "." or ".." components. Mount
points for a filesystem may appear on multiple lines each with different sets of hosts and
The second component of a line specifies how the filesystem is to be exported to the host
set. The option flags specify whether the filesystem is exported read-only or read-write
and how the client uid is mapped to user credentials on the server.
Export options are specified as follows:
-maproot=user The credential of the specified user is used for remote access by root. The
credential includes all the groups to which the user is a member on the local machine (see
id(1) ). The user may be specified by name or number.
-maproot=user:group1:group2:... The colon separated list is used to specify the precise cre-
dential to be used for remote access by root. The elements of the list may be either names
or numbers. Note that user: should be used to distinguish a credential containing no groups
from a complete credential for that user.
-mapall=user or -mapall=user:group1:group2:... specifies a mapping for all client uids
(including root) using the same semantics as -maproot.
The option -r is a synonym for -maproot in an effort to be backward compatible with older
export file formats.
In the absence of -maproot and -mapall options, remote accesses by root will result in using
a credential of -2:-2. All other users will be mapped to their remote credential. If a
-maproot option is given, remote access by root will be mapped to that credential instead of
-2:-2. If a -mapall option is given, all users (including root) will be mapped to that cre-
dential in place of their own.
The -kerb option specifies that the Kerberos authentication server should be used to authen-
ticate and map client credentials. This option requires that the kernel be built with the
The -ro option specifies that the filesystem should be exported read-only (default
read/write). The option -o is a synonym for -ro in an effort to be backward compatible with
older export file formats.
The third component of a line specifies the host set to which the line applies. The set may
be specified in three ways. The first way is to list the host name(s) separated by white
space. (Standard internet ``dot'' addresses may be used in place of names.) The second way
is to specify a ``netgroup'' as defined in the netgroup file (see netgroup(5) ). The third
way is to specify an internet subnetwork using a network and network mask that is defined as
the set of all hosts with addresses within the subnetwork. This latter approach requires
less overhead within the kernel and is recommended for cases where the export line refers to
a large number of clients within an administrative subnet.
The first two cases are specified by simply listing the name(s) separated by whitespace.
All names are checked to see if they are ``netgroup'' names first and are assumed to be
hostnames otherwise. Using the full domain specification for a hostname can normally cir-
cumvent the problem of a host that has the same name as a netgroup. The third case is spec-
ified by the flag -network=netname and optionally -mask=netmask. If the mask is not speci-
fied, it will default to the mask for that network class (A, B or C; see inet(5) ).
/usr /usr/local -maproot=0:10 friends
/usr -maproot=daemon grumpy.cis.uoguelph.ca 220.127.116.11
/usr -ro -mapall=nobody
/u -maproot=bin: -network 131.104.48 -mask 255.255.255.0
/u2 -maproot=root friends
/u2 -alldirs -kerb -network cis-net -mask cis-mask
Given that /usr, /u and /u2 are local filesystem mount points, the above example specifies
the following: /usr is exported to hosts friends where friends is specified in the netgroup
file with users mapped to their remote credentials and root mapped to uid 0 and group 10.
It is exported read-write and the hosts in ``friends'' can mount either /usr or /usr/local.
It is exported to 18.104.22.168 and grumpy.cis.uoguelph.ca with users mapped to their remote
credentials and root mapped to the user and groups associated with ``daemon''; it is
exported to the rest of the world as read-only with all users mapped to the user and groups
associated with ``nobody''.
/u is exported to all hosts on the subnetwork 131.104.48 with root mapped to the uid for
``bin'' and with no group access.
/u2 is exported to the hosts in ``friends'' with root mapped to uid and groups associated
with ``root''; it is exported to all hosts on network ``cis-net'' allowing mounts at any
directory within /u2 and mapping all uids to credentials for the principal that is authenti-
cated by a Kerberos ticket.
/etc/exports The default remote mount-point file.
netgroup(5), mountd(8), nfsd(8), showmount(8)
The export options are tied to the local mount points in the kernel and must be non-contra-
dictory for any exported subdirectory of the local server mount point. It is recommended
that all exported directories within the same server filesystem be specified on adjacent
lines going down the tree. You cannot specify a hostname that is also the name of a net-
group. Specifying the full domain specification for a hostname can normally circumvent the
BSD March 29, 1995 BSD
All times are GMT -4. The time now is 05:50 AM.