In the example above, /data is not within /export, so we export /export/data,
and specify that the /data directory should be bound to that name. The directory
/export/data must exist and should normally be empty.
When clients mount from this server, they just mount servername:/ rather than
servername:/export. It is not necessary to mount servername:/data, because
it will automatically appear beneath wherever servername:/ was mounted.
28.5.1.2 /etc/syscong/nfs
The /etc/sysconfig/nfs le contains a few parameters that determine NFSv4
server daemon behavior. Importantly, the parameter NFS4_SUPPORT must be set to
yes. NFS4_SUPPORT determines whether the NFS server supports NFSv4 exports
and clients.
28.5.1.3 /etc/idmapd.conf
Every user on a Linux machine has a name and ID. idmapd does the name-to-ID mapping
for NFSv4 requests to the server and replies to the client. It must be running on both
server and client for NFSv4, because NFSv4 uses only names for its communication.
Make sure that there is a uniform way in which usernames and IDs (uid) are assigned
to users across machines that might probably be sharing le systems using NFS. This
can be achieved by using NIS, LDAP, or any uniform domain authentication mechanism
in your domain.
The parameter Domain must be set the same for both, client and server in the /etc/
idmapd.conf le. If you are not sure, leave the domain as localdomain in the
server and client les. A sample conguration le looks like the following:
[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = localdomain
[Mapping]
Nobody-User = nobody
Nobody-Group = nobody
Sharing File Systems with NFS 475
