Re: [nfsv4] Asking for details about OPEN_DOWNGRADE

["Halevy, Benny" <bhalevy at panasas.com>]

Well it could be a script too.  These might be rewritten more frequently.
 
Benny

________________________________

From: nfsv4-bounces at ietf.org on behalf of Rick Macklem
Sent: Wed 2008-06-25 23:43
To: J. Bruce Fields
Cc: Steven Huntington; nfsv4 at ietf.org; Trond Myklebust
Subject: Re: [nfsv4] Asking for details about OPEN_DOWNGRADE





On Wed, 25 Jun 2008, J. Bruce Fields wrote:

>
> At least in the case of the linux server, if an nfsv4 client has a file
> open for write, then the server holds that file open.  So if a client
> has a file open for write on the server, then a user on the server that
> tries to execute that file will get ETXTBUSY.
>
> So in theory failing to open_downgrade could lead to spurious
> ETXTBUSY's.
>
Ok, now I understand. To be honest, I think I can live with it, since
about the only time an executable file will be open for writing is when
it's being compiled and it should be closed when the compile is done.

rick, who is too lazy to implement the open downgrade stuff correctly.

_______________________________________________
nfsv4 mailing list
nfsv4 at ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4


_______________________________________________
nfsv4 mailing list
nfsv4 at ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4