Date: Mon, 05 May 2003 10:54:47 -0500 From: Kirk Strauser <kirk@strauser.com> To: freebsd-hackers@freebsd.org Subject: Re: Periodic email about security notifications Message-ID: <87llxl4ce0.fsf@pooh.honeypot.net> In-Reply-To: <20030505153116.GC74924@freepuppy.bellavista.cz> (Roman Neuhauser's message of "Mon, 5 May 2003 17:31:16 %2B0200") References: <20030504100447.GU12792@freepuppy.bellavista.cz> <200305042336.h44NaoM7023683@gw.catspoiler.org> <20030504235059.GB42024@isnic.is> <20030505001955.GB92114@opiate.soulwax.net> <87r87d5vfg.fsf@pooh.honeypot.net> <87u1c94epk.fsf@pooh.honeypot.net> <20030505153116.GC74924@freepuppy.bellavista.cz>
index | next in thread | previous in thread | raw e-mail
At 2003-05-05T15:31:16Z, Roman Neuhauser <neuhauser@bellavista.cz> writes:
> or something like this?
>
> security_advisory_mirror_list="ftp0 ftp1 ftp2 ftp3 ftp4 ftp5 ftp6 ftp7"
>
> getMirror () {
> set -- $security_advisory_mirror_list
> security_advisory_mirror=$(eval echo '$'`jot -r 1 1 $#`)
> }
There's nothing at all wrong with that. My goal, though was to
automatically add that functionality to *every* program that would
ordinarily connect to ftp.freebsd.org. With the exception of changing some
default values, no programs would have to be modified to get the new
rotating-mirror capability.
Beyond that, someone could run a monitoring program that would take ailing
servers out of the DNS rotation as problems occur. With an automated setup,
you could be guaranteed that a connection to "ftpmirror.freebsd.org" would
always work (given a short interval to allow DNS updates to propogate).
--
Kirk Strauser
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87llxl4ce0.fsf>