From: "Lever, Charles" Subject: RE: NFS over TCP: random drop Date: Tue, 16 Mar 2004 09:19:22 -0800 Sender: nfs-admin@lists.sourceforge.net Message-ID: <482A3FA0050D21419C269D13989C61130435DD75@lavender-fe.eng.netapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: "Olaf Kirch" , Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1B3IE2-00066b-03 for nfs@lists.sourceforge.net; Tue, 16 Mar 2004 09:19:34 -0800 Received: from mx01.netapp.com ([198.95.226.53]) by sc8-sf-mx1.sourceforge.net with esmtp (Exim 4.30) id 1B3IE1-0002H3-9b for nfs@lists.sourceforge.net; Tue, 16 Mar 2004 09:19:33 -0800 To: "Trond Myklebust" Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: > a server which is=20 > accepting a connection then immediately breaking it is=20 > fundamentally broken... agreed that this should be rare behavior. but i can't think of a way to eliminate every case where a server might RST a TCP connection just after accepting it. cluster failover is one example where a server might legitimately RST a connection just after accepting it. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs