Common Faults of nfs construction in linux

For more information about common faults of nfs setup in linux-Linux Enterprise applications-Linux server applications, see the following. I was just getting started with the linux operating system. I have a general understanding of various features, but I have encountered a lot of trouble while building an nfs File Server recently.

As we all know, nfs file service is suitable for pure linux operating systems. Of course, win is also acceptable. It requires third-party software, and the speed is slow. It is fatal for file servers. I used the red hat Enterprise 4.0.nfs service which has been installed in the operating system. At this time, I only need to start the two basic services, then, I used vi editing to modify its/etc/exports according to the process, and the reading result also showed normal. shoemount-e can also see the Mount directory. It seems that everything is normal. After I configure the IP address, after the machine is restarted once, it can be pinged by using another linux server, but I can see its root directory (the client will never have a problem ), at first, I suspected that the IP address was faulty due to restart, but it was quickly ruled out. Then I suspect that the exports file is not edited. However, the request is denied. After the discount, I changed the mounted directory and hard disk settings. The problem persists. Finally, I accidentally restarted the nfs and portmap services and found that the problem was solved.

But I didn't stop the service. How can I automatically stop it? Later, I used the chkconfig -- list command to view it. Only when the two services are off in init 3, the real reason is found. It seems that this check is very important during service configuration!

Author: furious rescue