From owner-freebsd-current Mon May 15 10:36:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B40E537B9E0 for ; Mon, 15 May 2000 10:36:54 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id TAA06342; Mon, 15 May 2000 19:36:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nick Hibma Cc: Christian Weisgerber , freebsd-current@FreeBSD.ORG Subject: Re: cvsup on recent -CURRENT In-reply-to: Your message of "Mon, 15 May 2000 15:41:07 BST." Date: Mon, 15 May 2000 19:36:38 +0200 Message-ID: <6340.958412198@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Nick Hibma wri tes: >> On this machine which runs -CURRENT from two days ago or so, I'm >> seeing frequent cvsup client failures of this type: >> >> TreeList failed: Network write failure: Connection closed >> >> I don't recall ever running into this before. > >Which host are you pilling from? I am slurping things out of >cvsup.uk.freebsd.org and see the same messages. I thought it was crappy >modem connection. Try to disable the newreno stuff. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message