Table of Contents
Advertisement
•
— This process is the NFS server. It works with the Linux kernel to meet the
rpc.nfsd
dynamic demands of NFS clients, such as providing server threads each time an NFS client
connects. This process corresponds to the
•
— An optional process that allows NFS clients to lock files on the server. This
rpc.lockd
process corresponds to the
•
— This process implements the Network Status Monitor (NSM) RPC protocol
rpc.statd
which notifies NFS clients when an NFS server is restarted without being gracefully brought
down. This process is started automatically by the
configuration. This is not used with NFSv4.
•
— This process provides user quota information for remote users. This process
rpc.rquotad
is started automatically by the
•
— This process provides NFSv4 client and server upcalls which map between
rpc.idmapd
on-the-wire NFSv4 names (which are strings in the form of user@domain) and local UIDs and
GIDs. For
to function with NFSv4, the
idmapd
service is required for use with NFSv4.
•
— This process is used by the NFS server to perform user authentication and is
rpc.svcgssd
started only when
SECURE_NFS=yes
•
— This process is used by the NFS server to perform user authentication and is
rpc.gssd
started only when
SECURE_NFS=yes
1.2. NFS and
portmap
Note
The following section only applies to NFSv2 or NFSv3 implementations that
require the
The
service under Linux maps RPC requests to the correct services. RPC processes
portmap
notify
when they start, revealing the port number they are monitoring and the RPC
portmap
program numbers they expect to serve. The client system then contacts
with a particular RPC program number. The
port number so it can communicate with the requested service.
Because RPC-based services rely on
requests,
must be available before any of these services start.
portmap
The
service uses TCP wrappers for access control, and access control rules for
portmap
affect all RPC-based services. Alternatively, it is possible to specify access control
portmap
rules for each of the NFS RPC daemons. The man pages for
contain information regarding the precise syntax for these rules.
nfs
service. This is not used with NFSv4.
nfslock
service and does not require user configuration.
nfs
is set in the
is set in the
service for backward compatibility.
portmap
portmap
to make all connections with incoming client
portmap
service.
service and does not require user
nfslock
must be configured. This
/etc/idmapd.conf
/etc/sysconfig/nfs
/etc/sysconfig/nfs
service redirects the client to the proper
rpc.mountd
NFS and
portmap
file.
file.
on the server
portmap
and
rpc.statd
133
Advertisement
Table of Contents
