From owner-freebsd-stable Sun Nov 19 18:51: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id AD10237B479 for ; Sun, 19 Nov 2000 18:50:54 -0800 (PST) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id VAA94420; Sun, 19 Nov 2000 21:44:41 -0500 (EST) (envelope-from fran@reyes.somos.net) Message-Id: <200011200244.VAA94420@sanson.reyes.somos.net> From: "Francisco Reyes" To: "stable@FreeBSD.ORG" , "Zero Sum" Date: Sun, 19 Nov 2000 21:23:24 -0500 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: <00111819493901.09278@shalimar.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: New US CVSup mirrors Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Nov 2000 19:49:39 +1100, Zero Sum wrote: >... but couldn't you make a small >mod to the CVSsup server such that when over loaded, it requested from >FreeBSD.org, the name of a (nearby?) server that had been updated beyond >the rwquesting client and redirect the session to that server? >Surely it wouldn't be to hard to have the mirroring software report back up >the chain. That may not be "easy" for several reasons (i.e. determining the nearest server to you, etc..". Another possible alternative. How about allowing the client to get two or more servers. If the first one is busy try the next in the list. This would allow people to select the nearest servers and if one is busy go to the next. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message