From owner-freebsd-current Sun Oct 22 10:52:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id E6ECB37B4FE for ; Sun, 22 Oct 2000 10:52:56 -0700 (PDT) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id A65053E5A; Sun, 22 Oct 2000 19:52:51 +0200 (CEST) Date: Sun, 22 Oct 2000 19:52:51 +0200 From: Jesper Skriver To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: CVSUP access Message-ID: <20001022195251.C33499@skriver.dk> References: <5.0.0.25.2.20001022131711.023784c0@216.67.14.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.2.20001022131711.023784c0@216.67.14.69>; from forrie@forrie.com on Sun, Oct 22, 2000 at 01:19:01PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 22, 2000 at 01:19:01PM -0400, Forrest Aldrich wrote: > What's the latest scoop on cvsup access? Yesterday, I started up the > process in the early AM, returning late in the evening to find that it > still wasn't able to connect (connection limit exceeded). Which cvsup server are you using ? perhaps you could try an other ? /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message