Skip to main content

How to configure Network file system (NFS) client?

By
68.How to configure Network file system (NFS) client?
Ans.
1. To configure client, make sure that the portmapper, NFS file locking daemons statd & lockd, mount command are avaialbe.

 2. NFS client needs the portmapper running in order to process and route RPC calls and returns from the server to the appropriate port and programs.

 3. We can ensure portmapper is running or not by using following command:
#service portmap status

 4. If portmapper is not running then it’ll show us portmapper is stopped to start portmapper we’ll use following command:
#service portmap start

 5. Mounting can be done using following commands:
For example we wants to mount /media from the server configured at the end then we’ll execute following commands:
#mount –t nfs 192.168.166.5:/media /media

 6. If user wish, he/she can specify client mount options using mounts arguments as;
#mount –t nfs 192.168.166.5:/media /media -o resize=8292,wsize=8192, hard, nolock

 7. Following are the mounting options:
bg – Enables mount request to run in the background if first fails
fg – Enables mount request to run in the foreground if first fails
hard – Enables client to continue retrying if server does not respond
soft – Enables client operation to fail and terminate
tcp – Declares protocol to be tcp
udp – Declares protocols to be udp
resize=n – Declares read size of clients buffer
wsize=n – Declares write size of clients buffer
retry=n – Enables n retries for mounting
intr – Enables ctrl+c to work as interrupt
lock – Starts nfs locking via statd and lockd
nfsvers=n – Specifies versions of nfs
port=n – specifies nfs server port for connection

Labels:

Comments

Post a Comment

Popular posts from this blog

Explain the tools used to monitor system security.

By
12.Explain the tools used to monitor system security. Ans. 1. People who, for purpose of larceny or to amuse themselves, like to break into computers, they are called ‘crackers’. 2. If there is a vulnerability in a system they will find it and use it against you. 3. Preventing use of your machine for nefarious purpose and guarding against intrusion are, in the end, your responsibility alone. 4. Red hat equips you with tools to detect and deal with unauthorised access of many kinds. 5. You need to configure those tools and understand how to sense the warning they provide. 6. Fortunately Linux is development community is quick to find potential exploits and to create ways of slamming the doors before crackers can enter in your system. 7. Red hat is careful enough to making available new, patched version in which potential exploits have been found. 8. You should make sure to download and install the repaired package. 9. This line of defence...
Post a Comment
Read more

Explain the rc script and how they can be managed by manually.

By
18.Explain the rc script and how they can be managed by manually. Ans. 1. ‘rc’ scripts are stored in ‘/etc/rc.d’ directory, rc scripts are used to stop and start services for runlevels. 2. In ‘/etc/rc.d’ directory we have some additional directories rc0.d, rc1.d, rc2.d, rc3.d, rc4.d, rc5.d and rc6.d, the numbers in directory name corresponds to the runlevel and contains the scripts for runlevels. 3. For example let’s take runlevel 5, init program looks in the ‘/etc/rc.d/rc5.d/’ directory for the processes to start and stop. 4. All the scripts in the rc5.d directory are symbolic like to the actual scripts that are located in the ‘/etc/rc.d/init.d/’ directory. The use of symbolic link means that the runlevel can be modified by adding or removing symlinks or changing the order the script run. 5. rc scripts contains symbolic links which can be modified to change the runlevels. 6. Symbolic links begins with a ‘k’ and a number or an ‘s’ and a number. Example: S25netfs -...
Post a Comment
Read more

Explain memory and virtual file system in Linux.

By
22.Explain memory and virtual file system in Linux. Ans. 1. These file systems do not exist on disk in the same way that traditional file systems do, they either exists entirely in the system memory or they are virtual because they are an interface to system devices. 2. cramfs: cramfs is designed to cram a file System onto a small flash memory device, so it is small, simple and able to compress things well. The largest file size is 16MB and the largest file system size is 256MB since cramfs is so compressed, it isn’t instantly updateable. 3. tmpfs: tmpfs is structured around the idea that whatever is put in the /tmp file system is accessed again shortly, tmpfs solely in memory, so what you put in /tmp doesn’t persist between reboots. 4. ramfs: ramfs is basically cramfs without the compression. 5. romfs: This is a read only file system that is mostly used for initial ramdisks of installation disks. It was designed to take up very little space, so you could fit a ke...
Post a Comment
Read more