From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: RE: historical question: nfs_rename()
Date: Tue, 18 Oct 2005 11:36:40 -0700
Message-ID: <1129660600.12268.38.camel@lade.trondhjem.org>
References: <044B81DE141D7443BCE91E8F44B3C1E288E57B@exsvl02.hq.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: nfs@lists.sourceforge.net
To: "Lever, Charles" <Charles.Lever@netapp.com>
In-Reply-To: <044B81DE141D7443BCE91E8F44B3C1E288E57B@exsvl02.hq.netapp.com>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

ty den 18.10.2005 klokka 11:15 (-0700) skreiv Lever, Charles:
> this is going in the right direction.
> 
> should we quickly look at other test cases?  what return code should/do
> you get when you try to rename a directory onto a target directory that
> still has stuff in it?

I think the server is going to have to handle that. There is no way for
the client to atomically check the directory for emptiness and rename.

> have you tested both the file onto directory and directory onto file
> cases?

Still untested, but the check I introduced should ensure that
file-onto-directory works as expected. The directory-onto-file behaviour
is unchanged.

Cheers,
  Trond


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs