[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf-nfsv4
Subject:    Re: [nfsv4] NFS4ERR_CLID_INUSE when SetClientID changes
From:       Jim Rees <rees () umich ! edu>
Date:       2004-12-16 15:53:16
Message-ID: 20041216155316.D74151BB67 () citi ! umich ! edu
[Download RAW message or body]

  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


[prev in list] [next in list] [prev in thread] [next in thread]