From owner-freebsd-current Mon May 31 17:15:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-41.ppp.wenet.net [206.15.85.41]) by hub.freebsd.org (Postfix) with ESMTP id C05B814E4C for ; Mon, 31 May 1999 17:15:23 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id RAA00783; Mon, 31 May 1999 17:15:13 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Mon, 31 May 1999 17:15:13 -0700 (PDT) From: Alex Zepeda To: John Polstra Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The basic problem is in the phrase "a timestamp of the last time > they updated from freefall." There is no single timestamp that is > representative of an update. Suppose I start an update at 15:00:00 > UTC, and it finishes at 15:10:00. Every file updated came from > a snapshot at some point of time in that range. In other words, > CVSup can't take an instantaneous, coherent snapshot of the entire > repository and give it to you. How could it, given that a tree walk > alone over the repository takes a couple minutes? Since cvsup can take a revision of a file from a given time, why not use the time that the cvsup was started, this way it will ignore anything that was modified while cvsup was running, and the mirror can say, all the files are from xx.yy.zz point in time. And then have xntpd or somesuch running, so that all the cvsup mirrors have the same idea of when xx.yy.zz was.. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message