NFS Services
All NFS versions rely on Remote Procedure Calls (RPC) between clients and servers. RPC services under Red Hat Enterprise Linux 6 are controlled by the rpcbind service. To share or mount NFS file systems, the following services work together.
rpcbind
(portmap in older versions of Linux) The primary daemon upon which all the others rely, rpcbind manages connections for applications that use the RPC specification. By default, rpcbind listens to TCP port 111 on which an initial connection is made. This is then used to negotiate a range of TCP ports, usually above port 1024, to be used for subsequent data transfers. You need to run rpcbind on both the NFS server and client. This is not used with NFSv4.
service nfs start Starts the RPC processes needed to serve shared NFS file systems. The nfs daemon needs to be run on the NFS server only.
nfslock
service nfslock start Used to allow NFS clients to lock files on the server via RPC processes. The nfslock daemon needs to be run on both the NFS server and client.
netfs
Allows RPC processes run on NFS clients to mount NFS filesystems on the server. The netfs daemon needs to be run on the NFS client only.
The following RPC processes facilitate NFS services:
rpc.mountd: This process is used by an NFS server to process MOUNT requests from NFSv2 and NFSv3 clients.
rpc.nfsd: rpc.nfsd allows explicit NFS versions and protocols the server advertises to be defined.
Lockd: lockd is a kernel thread which runs on both clients and servers. It implements the Network Lock Manager (NLM) protocol, which allows NFSv2 and NFSv3 clients to lock files on the server.
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. This is not used with NFSv4.
rpc.rquotad: This process provides user quota information for remote users.
rpc.idmapd: rpc.idmapd provides NFSv4 client and server upcalls, which map between on-the-wire NFSv4 names.
The following RPC processes facilitate NFS services:
rpc.mountd: This process is used by an NFS server to process MOUNT requests from NFSv2 and NFSv3 clients.
rpc.nfsd: rpc.nfsd allows explicit NFS versions and protocols the server advertises to be defined.
Lockd: lockd is a kernel thread which runs on both clients and servers. It implements the Network Lock Manager (NLM) protocol, which allows NFSv2 and NFSv3 clients to lock files on the server.
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. This is not used with NFSv4.
rpc.rquotad: This process provides user quota information for remote users.
rpc.idmapd: rpc.idmapd provides NFSv4 client and server upcalls, which map between on-the-wire NFSv4 names.
The daemons are all part of the nfs-utils package, and may be either in the /sbin directory or the /usr/sbin directory.
If your distribution does not include them in the startup scripts, then then you should add them, configured to start in the following order:
rpc.portmap
rpc.mountd, rpc.nfsd
rpc.statd, rpc.lockd (if necessary), and rpc.rquotad
If your distribution does not include them in the startup scripts, then then you should add them, configured to start in the following order:
rpc.portmap
rpc.mountd, rpc.nfsd
rpc.statd, rpc.lockd (if necessary), and rpc.rquotad
No comments:
Post a Comment