From owner-freebsd-current Thu Oct 12 7:35:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 74B7A37B502; Thu, 12 Oct 2000 07:35:39 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id PAA80294; Thu, 12 Oct 2000 15:35:38 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id PAA09535; Thu, 12 Oct 2000 15:33:57 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 12 Oct 2000 15:33:57 +0100 To: John Baldwin From: Bob Bishop Subject: RE: -current grinds exceeding slow Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 11:42 -0700 11/10/00, John Baldwin wrote: >On 10-Oct-00 Bob Bishop wrote: >> Hi, >> >> What's happened recently to make -current so slow? >> [etc] > >I don't know. Can you try to narrow down the date by cvsupping or >cvs updating with date tags to see when it started slowing down? More data: it's networking that's doing it, not NFS per se. I'm doing a build with local sources on one of the affected boxes, on first impression looks like that is up to speed. Both my affected boxes have ed NICs, I'll see if I can scare up a different card to try in case it's the ed driver. Watch this space... -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message