On Fri, Jan 21, 2000 at 11:06:40PM +0100, Andre Oppermann wrote:
> Garance A Drosihn wrote:
> >
> > At 10:43 AM -0800 1/21/00, John Polstra wrote:
> > >This is another in my series of occasional nags to try to get people
> > >to use some of the less heavily loaded CVSup mirrors. In the US
> > >alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org.
> > >The newest, cvsup8, is a very high-capacity and well-connected site,
> > >yet hardly anybody is using it. Please give it a try!
> >
> > Maybe you should make cvsup.freebsd.org as a rotary (of sorts),
> > which returns a different IP address based on the callers IP
> > address. (or is that even possible?) That way, any given
> > host will always try the same cvsup server, but you'll be
> > spreading the load out among the servers.
>
> Thats not so easy. What about this:
>
> cvsup IN CNAME cvsup1.freebsd.org.
> cvsup IN CNAME cvsup2.freebsd.org.
> cvsup IN CNAME cvsup3.freebsd.org.
> cvsup IN CNAME cvsup4.freebsd.org.
> cvsup IN CNAME cvsup5.freebsd.org.
> cvsup IN CNAME cvsup6.freebsd.org.
> cvsup IN CNAME cvsup7.freebsd.org.
> cvsup IN CNAME cvsup8.freebsd.org.
>
> If you simply put "cvsup.freebsd.org" into your supfile you'll get
> randomly one of them. This should spread the load fairly well. If
> you want a special one then simply put "cvsupX.freebsd.org" into
> you supfile.
>
> Aint that easy?
>
> I don't see any appearant reson (short of network connectivity) that
> one *needs* to get always the *same* server.
This has been discussed regulary ...
You will risk hitting 2 different server in 2 rapid cvsup run's, where
the first may be more up to date than the next, as Jordan wrote earlier
in this thread ...
/Jesper
--
Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456
Work: Network manager @ AS3292 (Tele Danmark DataNetworks)
Private: Geek @ AS2109 (A much smaller network ;-)
One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
