"locally" means server-side or server-initiated rather than using the client-submitted gids,

and the server will perform the lookup according to the configured provider

for the access zone, e.g. LDAP (yeah kind of "remote", but again,

"local" just stands for "not NFS client").

The Isilon way for doing this is:

isi nfs settings export modify  --map-lookup-uid yes

hth

-- Peter

not sure

( from onefs 8.0.0 CLI administration Guide )

--map-lookup-uid {yes | no} If set to yes, incoming UNIX user identifiers (UIDs) will be looked up locally. The default setting is no.

this refers to uid rather than gid. If the list of GID's that are potentially wrong ( cut off at 16, but UID could exist in more than 16 groups ), unless the above option implicitly also does GID lookups ?

Be careful with this option because it can generate some significant load on the LDAP infrastructure depending upon the number of users connecting.  I'm not saying don't use it, just instead watch your ldap infrastructure carefully if you do. And yes lookup the UID not the GID, because looking up the UID will return the UID/GID and all the supplemental secondary groups (even more than 16).

~Chris

any thoughts on how to measure/monitor this load, as while the documentation is heavy on the warnings, its very light on practical ways to measure.