From owner-freebsd-current Mon May 15 14:45: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D18D37B8B9 for ; Mon, 15 May 2000 14:44:52 -0700 (PDT) (envelope-from daemon@mips.inka.de) Received: from bigeye.rhein-neckar.de (uucp@) by mail.inka.de with local-bsmtp id 12rSfP-0006eQ-01; Mon, 15 May 2000 23:44:47 +0200 Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id WAA97895 for freebsd-current@freebsd.org; Mon, 15 May 2000 22:52:47 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: cvsup on recent -CURRENT Date: 15 May 2000 22:52:46 +0200 Message-ID: <8fpo2u$2viq$1@bigeye.rhein-neckar.de> References: <20000510191545.A72939@fettuccini.unix-ag.uni-kl.de> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (My original question should have gone out last Thursday but had been stuck in a mail queue since.) Nick Hibma wrote: > > TreeList failed: Network write failure: Connection closed > > Which host are you pilling from? I am slurping things out of > cvsup.uk.freebsd.org and see the same messages. The problem was most apparent with cvsup.uk.openbsd.org, which is probably the same machine. It was less severe with cvsup.pasta.cs.uit.no, and didn't occur at all with cvsup3.de.freebsd.org and for localhost connections. Disabling newreno sysctl -w net.inet.tcp.newreno=0 immediately fixed the problem, so I guess we have the culprit there. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message