From owner-freebsd-questions Thu Jul 25 16:09:02 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA08721 for questions-outgoing; Thu, 25 Jul 1996 16:09:02 -0700 (PDT) Received: from gamespot.com (ns1.gamespot.com [206.169.18.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA08716 for ; Thu, 25 Jul 1996 16:09:00 -0700 (PDT) Received: from tech-a.gamespot.com (tech-a.gamespot.com [206.169.18.59]) by gamespot.com (8.6.12/8.6.12) with SMTP id PAA24376 for ; Thu, 25 Jul 1996 15:58:43 GMT Message-Id: <199607251558.PAA24376@gamespot.com> Comments: Authenticated sender is From: "Ian Kallen" To: questions@freebsd.org Date: Thu, 25 Jul 1996 16:03:42 +0000 Subject: src-lib errors from all sup servers?? Reply-to: ian@gamespot.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I continue to try a migration from 2.1.0 to 2.1.5-stable... The only sup servers that I've found to be responsive at all (sup and sup5) both choke with "Read error on network: Connection reset by peer" message when it gets to src-lib. Also having aborted updates for usr-sbin -- how does anybody find sup useful at all with such poorly functioning services? Obviously folks are using a more expeditious method to upgrade, sup has been painfully slow and haphazard. I've been at it for about 18 hours now and the problem is not bandwidth..... Ian Kallen ian@gamespot.com Director of Technology & Web Administration http://www.gamespot.com