Subject: Re: [nfsv4] NFS4ERR_CLID_INUSE when SetClientID changes authenticationmechanisms

From: Jim Rees <[email-masked]>
Date: Thu, 16 Dec 2004 10:53:16 -0500

Could it get away with just keeping no state for untrusted clients, and
  treating setclientid (and open, close, etc.) as no-ops?

The client should be ok with that, but what would you do about conflicting
locks?

_______________________________________________
nfsv4 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nfsv4