Re: [nfsv4] NFS4ERR_CLID_INUSE when SetClientID changes authenticationmechanisms

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Jim Rees (rees@umich.edu)
Date: 12/16/04-09:53:16 AM Z 

Subject: Re: [nfsv4] NFS4ERR_CLID_INUSE when SetClientID changes authenticationmechanisms 
From: Jim Rees <rees@umich.edu>
Date: Thu, 16 Dec 2004 10:53:16 -0500
Message-Id: <20041216155316.D74151BB67@citi.umich.edu>

  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
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-02:13:47 AM Z CST