From owner-freebsd-stable Sat Nov 18 8:15: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id EA59237B479 for ; Sat, 18 Nov 2000 08:15:04 -0800 (PST) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 13xAdo-000CyQ-00; Sat, 18 Nov 2000 08:15:00 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Randy Bush To: "Rodney W. Grimes" Cc: davids@webmaster.com (David Schwartz), freebsd-stable@FreeBSD.ORG (FreeBSD Stable) Subject: Re: New US CVSup mirrors References: <200011181604.IAA14339@gndrsh.dnsmgr.net> Message-Id: Date: Sat, 18 Nov 2000 08:15:00 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually any perl weenie worth $15.00 hour should be able to codify a fully > automated solution to this problem in less than 8 hours. > > cvsup-master.freebsd.org already has the data on what servers are actively > updating from the master via the cvsupd.log file. Infact it knows exactly > what collection was updated on what server at what time. > > Prune that data to a list of ``active and reasonably up to date servers'' > and send dynamic DNS updates... viola automagic system. Hell we had a perl > hacker around here that made ${User}.portmaster.isp.com track who had what > IP address assigned when they logged in via dynamic DNS. turns out that, in operational reality, these hacks don't scale. they are not stable, they rely on centralization, ... they'll work for a small game, but the problems increase super-linearly with scale. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message