Installation guide

NFS Client Configuration
59
rpc.nfsd
rpc.nfsd allows explicit NFS versions and protocols the server advertises to be defined. It works
with the Linux kernel to meet the dynamic demands of NFS clients, such as providing server
threads each time an NFS client connects. This process corresponds to the nfs service.
rpc.lockd
rpc.lockd allows NFS clients to lock files on the server. If rpc.lockd is not started, file
locking will fail. rpc.lockd implements the Network Lock Manager (NLM) protocol. This process
corresponds to the nfslock service. This is not used with NFSv4.
rpc.statd
This process implements the Network Status Monitor (NSM) RPC protocol, which notifies NFS
clients when an NFS server is restarted without being gracefully brought down. rpc.statd is
started automatically by the nfslock service, and does not require user configuration. This is not
used with NFSv4.
rpc.rquotad
This process provides user quota information for remote users. rpc.rquotad is started
automatically by the nfs service and does not require user configuration.
rpc.idmapd
rpc.idmapd provides NFSv4 client and server upcalls, which map between on-the-wire NFSv4
names (which are strings in the form of user@domain) and local UIDs and GIDs. For idmapd to
function with NFSv4, the /etc/idmapd.conf must be configured. This service is required for
use with NFSv4, although not when all hosts share the same DNS domain name.
10.2. NFS Client Configuration
The mount command mounts NFS shares on the client side. Its format is as follows:
mount -t nfs -o options host:/remote/export /local/directory
This command uses the following variables:
options
A comma-delimited list of mount options; refer to Section 10.4, “Common NFS Mount Options” for
details on valid NFS mount options.
server
The hostname, IP address, or fully qualified domain name of the server exporting the file system
you wish to mount
/remote/export
The file system / directory being exported from server, i.e. the directory you wish to mount
/local/directory
The client location where /remote/export should be mounted
The NFS protocol version used in Red Hat Enterprise Linux 6 is identified by the mount options
nfsvers or vers. By default, mount will use NFSv4 with mount -t nfs. If the server does not
support NFSv4, the client will automatically step down to a version supported by the server. If you use
the nfsvers/vers option to pass a particular version not supported by the server, the mount will fail.
The file system type nfs4 is also available for legacy reasons; this is equivalent to running mount -t
nfs -o nfsvers=4 host:/remote/export /local/directory.
Refer to man mount for more details.