Harry Putnam wrote:
Robert Thurlow <[email protected]> writes:
This makes a lot more sense. NFSv4 should have worked for you if you had the client and server both set to the same NFSv4 domain - if you care to work on this, we can.
Thanks for the offer. Is there something NFSv4 offers that would make it worth doing?
Probably the most tangible difference is the fact that a modern NFSv4 client will permit you to see child mounts, which we have sometimes called mirror mounts. With V3, the only way you can properly handle nested shares on a server is to list them all in an automounter map; with V4, they just show up properly. Linux clients and newer Nevada clients (post snv_77) will do this. And when I mention NFSv4 domain, it is not necessarily related to a DNS or NIS domain. They can be different, and sometimes just are different. This is about how a client or server converts a UID to a string like "[email protected]" as V4 needs it, and how the other end converts it back to a numeric UID. If the domains don't match, you see "nobody". I don't recall how to set or see the NFSv4 domain on Linux, but on Solaris you can see it with "cat /var/run/nfs4_domain" and set it in /etc/default/nfs. Rob T _______________________________________________ opensolaris-discuss mailing list [email protected]
