Hello! I just try to understand NFSv4 client-side attribute caching, if I do a nfs4client_setattr(), which attribute values can be updated in the clients cache, and which should be invalidated, and then reloaded from the server? For example if I do a nfs4client_setattr(FATTR4_WORD1_OWNER, "myusr1@mydom"): Can I cache "myusr1@mydom" as the new user on the client side on success, or should I invalidate the cache, because maybe the idmapd on the server changed the user name, or exports all_squash option squashed the user name to nobody? Dan -- Dan Shelton - Cluster Specialist Win/Lin/Bsd