From owner-freebsd-current Mon May 15 8: 0: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 5A8B137B61B for ; Mon, 15 May 2000 08:00:03 -0700 (PDT) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000515145957.RAJG18096.mail.rdc1.ct.home.com@home.com> for ; Mon, 15 May 2000 07:59:57 -0700 Message-ID: <392010CA.4A420033@home.com> Date: Mon, 15 May 2000 10:59:22 -0400 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.15 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: Re: cvsup on recent -CURRENT References: <20000510191545.A72939@fettuccini.unix-ag.uni-kl.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > > 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. > Same here. Last night was okay. It started about 5 days ago. If you just start over it usually finishes okay. -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message