On Mon, 2004-09-20 at 18:10, CB wrote: > On Tue, 2004-09-21 at 00:49, David L Norris wrote: > > On Mon, 2004-09-20 at 21:02 +1000, CB wrote: > > > /home-ext/<username> > > > 192.168.0.1/24(rw,wdelay,insecure,root_squash,no_subtree_check,fsid=0,anonuid=65563,anongid=65535) > > > > > Anyone know what I am doing wrong, or can suggest how to troubleshoot > > > further? > > > > What's with all the options? Have you tried exporting the home > > directory using simple options? Just divide and conquer the options > > until you find the one that is causing your problem. > > > > This should always work: > > /home 192.168.0.0/255.255.255.0(rw,root_squash) > > For some reason on my (FC2) system, the fsid option is necessary, but I > can get away without the other options, at least for testing purposes. > So that leaves me with: > > /home 192.168.0.0/255.255.255.0(rw,root_squash,fsid=0) > > (Without the fsid, I can't connect the client). > > But whichever options I do or don't use, I'm still finding that the UID > and GID of all files and dirs shown by ls -n in the user's home > directory once connected are 0 and 1 respectively, whereas on the server > they are 500 and 500. The upshot is that the user on the remote machine > only has read access to most of the home directory. > > Why would the UID and GID be different on the NFS and client machines? > If you read the manpage on exports, the section on user id mapping might prove useful. It also helps to read all the related man pages for something you are doing. (nfs, fstab, exports, mount, ets) You can try setting it up so the users home directory is mounted by that user when they login. (export each users home directory from the server). Use an option such as "user" or "users" in the fstab entry so it gets the users permissions and access at mount time.
