Skip to main content

Explain the NFS server daemons.

62.Explain the NFS server daemons.
Ans.
NFS server needs following daemons:
1. /sbin/rpc.lockd
It starts kernel’s lock manager.

2. /usr/sbin/rpc.mountd
It processes nfs client’s mount requests.

3. /usr/portmap
It allows client’s to discover services available on the NFS server.

4. /sbin/rpc.statd
It manages lock recovery in case of server crash

5. /usr/sbin/rpc.nfsd
It provides all nfs services other than file locking and quotas.

6. /usr/sbin/rpc.rquotad
It provides NFS client’s quota information of NFS exports.

7. rpc.gssd
Creates security contexts on RPC clients for exchanging RPC information using SecureRPC (RPCSEC) using GSS.

8. rpc.svcgssd
Creates security contexts on RPC servers for exchanging RPC information using SecureRPC (RPCSEC) using GSS.

9. rpc.idmapd
Maps local user and group names to NFSv4 IDs (and vice versa).

10. To start the NFS services there are two commands as follows:
#service nfs start
#/etc/rc.d/init.d/nfs.start

11. The startup scripts starts eight copies of nfsd to enable the server to process multiple request simultaneously. If user wants to change this value then edit /etc/sysconfig/nfs and add a line as follow:
RPSNFDCOUNT =n
n will be replaced by the number of nfsd process according to user.
Example:
#cat>/etc/sysconfig/nfs
RPSNFDCOUNT = 16

Comments

Popular posts from this blog

Java,ES,QT practical files

All practical files: Click below to start download Uploaded on special request||||

How to configure Network file system version 4 (NFSv4) client?

69.How to configure Network file system version 4 (NFSv4) client? Ans. 1. There are two new options listed in NFSv4 are introduced as: clientaddr and ports 2. The version 3 of NFS introduced NFS over TCP, which improved NFS’s reliability. 3. In NFSv3, users use the mount option i.e., tcp as client whether client wants to use TCP or UDP to communicate with the server. NFSv4 replaces tcp or udp with a single option i.e. ports=tcp or udp 4. The default buffer size for NFSv4 is 8192 bytes, but it can grow to as large and by 32,678 bytes, which results performance improvements. 5. Following are the mount options: clientaddr=n – Declares client to be multihomed proto=type – Declares port as either udp or tcp resize=n – declares read size of clients buffer wsize=n – Declares write size of clients buffer sec=mod – Declares security model as either krb, krb5 etc.

Board Question papers 2010-15

Click below to download