Novell LINUX ENTERPRISE SERVER 11 - ADMINISTRATION Administration Manual page 371

In the example above, /data is not below the /export, but we want to export it
anyway, 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, that should just mount servername:/ rather
than servername:/export. It is not necessary to also mount servername:/data
and that will automatically appear beneath wherever servername:/ was mounted.
/etc/sysconfig/nfs
This file contains a few parameters that determine NFSv4 server daemon behavior.
Importantly, the parameter NFSv4_SUPPORT must be set to yes. This parameter deter-
mines whether the NFS server supports NFSv4 exports and clients.
/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. This 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 file systems using NFS. This
can be achieved by using NIS, LDAP, or any uniform domain authentication mechanism
in your domain.
For proper function, the parameter Domain must be set the same for both, client and
server in this file. If you are not sure, leave the domain as localdomain in the server
and client files. A sample configuration file 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 357