932
edits
Changes
m
6. <li>On vm1 and vm3your nfs-client machine, un-mount the remote directory nfs-server:/nfs-pub with the command.umount /nfs-mntPlease Please note that this must be done by "root" and the directory /nfs-mnt is not being used by anyprocess.</li>7. <li>On the NFS server, make the following changes to the /etc/exports file:
→Investigation 3: File creation permission and user name mapping on NFS shares: - Formatting content for wiki
Again, make notes of the owner and group owner of the file.</li>
<li>Login to the NFS server, and examine the ownership of the files you just created. Who is the owner and the group owner of the respective files?</li>
change
<source>/nfs-pubip-of-vm1(rw, root_squash)</source>
to
<source>/nfs-pubchange/nfs-pubto/nfs-pubip-of-vm1(rw, root_squash)ip-of-vm1(rw, no_root_squash)ip-of-vm3(rw, root_squash)ip-of-vm3(rw, no_root_squash)</source>and re-export the directory.</li>8. <li>On vm1 and vm3the client, re-mount the share directory and repeat step 3 to step 6 under the super user
account "root" and copy the file /etc/group to the share directory /nfs-mnt with the
corresponding file name.</li>9. On vm1 and vm3, <li>un-mount the remote directory.</li>10.<li>On the NFS server, change the "rw" option in the /etc/exports file to "ro" and re-export thedirectory.</li>11.<li>On vm1 and vm3the client, re-mount the share directory and repeat step 3 to step 6 under the super user
account "root" and copy the file /etc/hosts to the share directory /nfs-mnt with the corresponding
file name.</li>ls -l <li>Observe how the different settings on the server affected the ownership and permissions of files created on the client side.</nfs-pub/passwd.A.*li><li>Repeat this investigation on vm3, naming the first user userB (or ls -l /nfs-pub/passwd.instead of userA), and replace the A in any file names with B.*) When creating files, try to check predict the file created by ownership and permissions of the user "userA" and "ops535" on vm1, vm3resulting files. </li>
</ol>
