I wonder how Solaris does it.
Not sure.
I think the rw= and root= information has to be checked for each NFS request. So that is the performance issue. I know for a fact that you can change the root= info on the NFS server, exportfs again, and the change happens on all NFS clients without having to umount and mount the volume again. In other words, on the NFS server you can unilaterally grant or remove root= access for actively mounted NFS clients.
All true statements but my point to NetApp was that if they have to check it for every request they should be able to cache it and check from there (cause they have to check somewhere) and I would be quite happy with a periodic update. I don't expect it to be to the second.
If these privileges were set at mount time, then you would have to unmount and mount again on NFS clients in order for the change to take effect.
That would be very bad... bad.... baddddddd. Obviously not an option.
I suppose the NFS server could cache the rw= and root= information for recently active NFS clients to avoid most netgroup queries.
See above.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support