1,381
edits
Changes
From IGEP - ISEE Wiki
→No summary
We’re using the same configuration options for both directories with the exception of no_root_squash. Let’s take a look at what each one means.
'''rw''': This option gives the client computer both read and write access to the volume. '''sync''': This option forces NFS to write changes to disk before replying. This results in a more stable and consistent environment since the reply reflects the actual state of the remote volume. However, it also reduces the speed of file operations. '''no_subtree_check''': This option prevents subtree checking, which is a process where the host must check whether the file is actually still available in the exported tree for every request. This can cause many problems when a file is renamed while the client has it opened. In almost all cases, it is better to disable subtree checking. '''no_root_squash''': By default, NFS translates requests from a root user remotely into a non-privileged user on the server. This was intended as security feature to prevent a root account on the client from using the file system of the host as root. no_root_squash disables this behavior for certain shares.
When you are finished making your changes, save and close the file. Then, to make the shares available to the clients that you configured, restart the NFS server with the following command:
sudo systemctl restart nfs-kernel-server
Before you can actually use the new shares, however, you’ll need to be sure that traffic to the shares is permitted by firewall rules
===Step 4 — Adjusting the Firewall on the Host===
First, let’s check the firewall status to see if it’s enabled and if so, to see what's currently permitted:
