On Mon, 18 Oct 2010 10:10:59 -0400 Jeff Layton <jlayton@xxxxxxxxxx> wrote: > See: > > http://nfs.sourceforge.net/ > > ...section D2. The faq mentions that NFSv4 could do away with it > because it's stateful, but that's not really the case either. > Section D2 ends with: "The NFS version 4 protocol is stateful, and could actually support delete-on-last-close. Unfortunately there isn't an easy way to do this and remain backwards-compatible with version 2 and 3 accessors." So, theoretically, could one modify the code to selectively disable silly rename on a client, when it knows it is talking v4 with the server? Thanks ClÃudio -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
