In the last episode (May 30), John Polstra said:
> Dan Nelson wrote:
> > A simple round-robin DNS for all the active cvsup servers should
> > suffice; make it cvsup.freebsd.org, stick it back in the sample
> > cvsup config files, and put a comment mentioning that if you only
> > cvsup once a day or less it will work fine.
> >
> > I think the only complaint about RR servers (the last time this was
> > brought up) was that if you cvsup'ed twice in a short period of
> > time, you might catch two servers with different update times
> > (differing by up to an hour).
>
> There were other objections which were serious to make me (hang on a
> second -- where is that CVSupMeister cap ... ah, there we go, it's in
> place now) decide not to do it. One objection was that a mirror
> might have been network-isolated from the master server for an
> extended period of time. In that case, you'd randomly get a _big_
> step backwards in time.
Any way to timestamp a CVS tree so that cvsup knows if its current tree
is "newer" than the one the server is trying to send it? It looks like
the "checkouts.cvs" file is updated every time cvsup is run; could this
be used as a timestamp? (this won't work for people cvsupping off
freefall directly, but since the public cvsupd servers use cvsup to
update themselves, cvsupd should be able to determine its own "last
update" time)
Alternatively, a script could be run every 8 hours or so that checks
all the members of the cvsup RR group and verifies that all servers are
uptodate. If one isn't, it is removed from the RR group until it
catches up. This is a bit more work but is certainly feasible.
-Dan Nelson
dnel...@emsphone.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
