NFS mounts here are not more than a few more, according to the steps in turn. There is a picture of the truth.
Server-side configuration:(IP 192.168.88.85)
1. View Software NFS Package installation
Rpm-qa |grep NFS
2. See if the rpcbind is installed
3 If installation is not installed:
4. See if there is a exports file
Cat/etc/exports
If you do not manually build the file in etc exports the content is written in: Need to mount folder directory
do not manually build files yourself. the content added inside is
/opt/tp-manager/data is the permission to mount the directory * (rw,no_root_squash) file (...). Self-check)
Service-side configuration complete
Client:The jar package that requires NFS is identical to the server 1, 22 operations.
3. Check whether the server is mounted (see precautions if there is no mount display)
SHOWMOUNT-E 192.168.88.15
4. Client mount command:mount-t NFS 192.168.88.15:/opt/tp-manager/data/opt/tp-worker/data
/opt/tp-manager/data is the path that the server side path mounts to the client:/opt/tp-worker/data
Mount Complete:
Precautions :
Service-side Modify exports file requires Operation command
EXPORTFS-RV (re-mount)
Service Rpcbind Restart
Service NFS Restart
Service iptables Stop (fire strong off must)
If the client wants to cancel the mount:umount-f/opt/tp-worker/data
Linux NFS Mount Configuration