From owner-freebsd-current Thu Jun 1 22:03:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA03326 for current-outgoing; Thu, 1 Jun 1995 22:03:29 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA03320 for ; Thu, 1 Jun 1995 22:03:28 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA27553; Thu, 1 Jun 95 22:56:31 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506020456.AA27553@cs.weber.edu> Subject: Re: sup is fetching whole src tree To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Date: Thu, 1 Jun 95 22:56:31 MDT Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199506012205.AAA10048@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Jun 2, 95 00:05:57 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.ORG Precedence: bulk > The international lines are (at least in the academic networks - WIN) > terribly slow these days. In addition to that it looks like > sup is fetching a whole src tree - my sup processes hang on fetching > the whole day and do not come to an end. > > Is it because the recent outages of thud/freefall? Or am I seeing > white mice? :-) As of this last Memorial Day weekend, AlterNet has replaced one or more [fried] ports on the router VIENNA1.VA.ALTERNET.NET. This is according to AlterNet themselves. There has also been some PacBell equipment dealing with leased lines in San Diego on the fritz the past couple of days; right now it seems to have been permanently fixed. The equipment for that particular interconnect has been replaced twice because of a cooling problem that they think is resolved (according to PacBell). The reroutining because of the bad port was bringing their ATM network to its knees because it was at near capacity (again, according to AlterNet -- please aregue that ATM is not an ugly baby with them, not me, Garrett). It was also affecting the SprintLink backbone which is ATM for similar reasons (this time according to Sprint -- again, you can argue that ATM isn't at fault with them, not me, since they are two of the larger ATM networks on the planet and they agree). Currently, the DC SprintLink hub (sl-dc-6-F0/0.sprintlink.net) is known to have at least one bad port (either the port going out to sl-dc-8-H1/0-T3.sprintlink.net or to sl-stk-5-H1/0-T3.sprintlink.net). Most other Internet backbone trouble spots are much less hot, at least as far as the US is concerned, as far as I know. Total downtime for this site has been a little over a week where the net was barely-usable-to-totally-unusable. I expect things will be happy until the next great catastrophe or until the backbone providers start sticking routing "fuses" for traffic overlead between their seperate backbones when the traffic originates on "alien" backbones. Oh, oh, what great fun we are having... Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.