From owner-freebsd-current@FreeBSD.ORG Sat Jan 10 11:15:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8CC116A4CE for ; Sat, 10 Jan 2004 11:15:15 -0800 (PST) Received: from cmsrelay02.mx.net (cmsrelay02.mx.net [165.212.11.111]) by mx1.FreeBSD.org (Postfix) with SMTP id 69B9C43D5C for ; Sat, 10 Jan 2004 11:15:13 -0800 (PST) (envelope-from noackjr@compgeek.com) Received: from uadvg129.cms.usa.net (165.212.11.129) by cmsoutbound.mx.net with SMTP; 10 Jan 2004 19:15:12 -0000 Received: from optimator.noacks.org [65.69.2.105] by uadvg129.cms.usa.net (ASMTP/noackjr@usa.net) via mtad (C8.MAIN.3.11E) with ESMTP id 095iaJTPJ0068M29; Sat, 10 Jan 2004 19:15:09 GMT X-USANET-Auth: 65.69.2.105 AUTH noackjr@usa.net optimator.noacks.org Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 1320DDE; Sat, 10 Jan 2004 13:15:09 -0600 (CST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08096-03; Sat, 10 Jan 2004 13:14:58 -0600 (CST) Received: from www.noacks.org (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with SMTP id 136F465; Sat, 10 Jan 2004 13:14:58 -0600 (CST) Received: from 192.168.1.10 (SquirrelMail authenticated user noackjr) by www.noacks.org with HTTP; Sat, 10 Jan 2004 13:14:58 -0600 (CST) Message-ID: <3189.192.168.1.10.1073762098.squirrel@www.noacks.org> In-Reply-To: <20040110181927.GA17659@electra.cse.Buffalo.EDU> References: <20040109121734.E78161-100000@moo.sysabend.org><87d69r4tsd.fsf@strauser.com> <20040110181927.GA17659@electra.cse.Buffalo.EDU> Date: Sat, 10 Jan 2004 13:14:58 -0600 (CST) From: "Jon Noack" To: "Ken Smith" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at noacks.org Content-Transfer-Encoding: quoted-printable cc: Kirk Strauser cc: freebsd-current@freebsd.org Subject: Re: Look ma, the kernel don't compile no more... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@compgeek.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2004 19:15:16 -0000 Ken Smith wrote: > On Sat, Jan 10, 2004 at 11:06:58AM -0600, Kirk Strauser wrote: >> Out of curiosity, why would multiple syncs be better than just one? >> Wouldn't the final sync be the same whether you'd done several before = it >> or not? > > It all depends on where you're sync-ing from. Keep in mind the > cvsup mirror sites are exactly that - mirrors. There is one > central CVS repository. If a developer is doing an update of the > main CVS repository as several commits there can be several minutes' > worth of time that what's in the CVS repository is "inconsistent" > because what s/he committed first contains things that depend on > things that s/he commits a little bit later (composing log messages > can take time, etc.). > > cvsup-master itself mirrors from the main CVS repository roughly > every 10 minutes I think. So if it takes a snapshot between the > developer's first and second commit and if you're using cvsup-master > as where you sync from then doing two sync's 10 to 20 minutes apart > can help with this sort of problem if you watch what gets updated > to watch for stuff that "seems related". > > Virtually every other public cvsup mirror site will be mirroring > from cvsup-master, but typically with about an hour between syncs. > > There are things that can make things a little bit more complicated > than this. For example last night's 5.2-RELEASE tag touches a huge > number of files. cvsup-master's load was around 50 for a while, and > it took one machine I was watching over an hour to do the first sync > after the tagging. A mirror site won't make changes 'visible' to > its downstream sites until it completes its own sync. The second cvsup could get you the first portion of another developer's update. Likewise for the third, fourth, etc. I think the most efficient way is to cvsup once and build. If the build fails, you can quite quickl= y check the commit logs (http://www.freshsource.org/commits.php is a great resource for this) and re-cvsup if necessary. If seems to me that multiple cvsups back-to-back are a drain on bandwidth and server load with dubious benefits. Jon Noack