Setclientid / Definition of client
Trond Myklebust
trond.myklebust at fys.uio.no
Mon Dec 4 11:35:23 EST 2006
On Mon, 2006-12-04 at 11:25 -0500, J. Bruce Fields wrote:
> On Mon, Dec 04, 2006 at 04:33:45PM +0100, Felix Engel wrote:
> > This implies that on the client side, for every system user (i.e. for
> > everyone making calls with unique credentials), a separate "nfs4 client"
> > as per the RFC should be generated.
>
> Not necessarily--multiple users should be able to use the state
> established by a setclientid performed by a single user. But of course
> if that single user goes away, then you're left with no way to
> reestablish the state that was held under the clientid established by
> that user.
Under what circumstances is that a problem? Normally, we just RENEW, and
if that fails, we assume we will need to re-establish state from
scratch.
> Which is why by default the linux client is set up to use machine
> credentials for this, which shouldn't ever go away. So at least if
> you're using a linux client, I don't think you should ever see the
> rq_cred be different for two subsequent setclientid calls.
No. The Linux client tries to use the creds of the first person to open
a file.
Cheers
Trond
More information about the NFSv4
mailing list