From: Trond Myklebust Subject: Re: Re: NFS as a Cluster File System. Date: Sun, 12 Jan 2003 22:29:50 +0100 Sender: nfs-admin@lists.sourceforge.net Message-ID: <15905.56910.633666.132328@charged.uio.no> References: Reply-To: trond.myklebust@fys.uio.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: alanr@unix.sh, nfs@lists.sourceforge.net Return-path: Received: from mons.uio.no ([129.240.130.14] ident=7411) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 18XpgB-0002MT-00 for ; Sun, 12 Jan 2003 13:30:03 -0800 To: "Lorn Kay" In-Reply-To: Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: >>>>> " " == Lorn Kay writes: > Meaning if you don't lock a file and just read it you may not > see the what another client has written to it, or is that not > an issue because the other client will have locked and then > unlocked the file when it is done making changes? Meaning that unless *all* clients lock the file prior to reading or writing from it (and then unlock it when done), there will be caching inconsistencies. Cheers, Trond ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs