In this chapter, we have examined the basic operation of the Network File System (NFS). This system is widely used to share volumes from servers to multiple clients, and is flexible enough to support systems that are both clients and servers. Since NFS is ubiquitous in the Solaris environment, administrators should be very familiar with the many configuration options available.
1. |
An NFS volume shared from a server to a client can be accessed by which of the following?
|
|
2. |
Which daemons must be run to support a NFS server?
|
|
3. |
Which of the following commands would share the volume /staff to the hosts georgia, carolina, and fairfax read-only using NFS?
|
|
4. |
Which of the following commands would stop sharing the volume /data using NFS?
|
|
5. |
Which of the following commands would mount the shared volume /data using NFS from the server zemindar (read-write) on the mount point /zemindar?
|
|
6. |
Which of the following commands would mount all partitions listed in /etc/vfstab that are not currently mounted?
|
|
7. |
Which of the following commands shows the local resources shared through the networked file systems that are currently mounted by specific clients?
|
|
8. |
What command resets nfsstat counters to zero?
|
|
9. |
Which of the following factors does not influence NFS server performance?
|
|
Answers
1. |
A. Any disk volume is always accessed through a mount point. |
2. |
B. Both nfsd and mountd must be running to support NFS services. |
3. |
D. Read-only is specified by using the ro option. |
4. |
C. Volumes can be unshared by using the unshare command. |
5. |
D. Read-write is specified by using the rw option. |
6. |
C. To mount all volumes, use mountall. |
7. |
A. The dfmounts command shows the local resources shared through NFS that are mounted. |
8. |
A. The nfsstat command counters must be reset with the -z option. |
9. |
D. The size of the kernel does not directly affect NFS performance. |