Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 9 Oct 2007 23:59:57 +0200
From:      Erwin Lansing <erwin@FreeBSD.org>
To:        freebsd-hubs@freebsd.org
Subject:   Re: public_distfiles mirroring delay
Message-ID:  <20071009215957.GZ73011@droso.net>
In-Reply-To: <1191962524.84549.6.camel@localhost>
References:  <1191962524.84549.6.camel@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help

--DWg365Y4B18r8evw
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 09, 2007 at 01:42:04PM -0700, Eric Anholt wrote:
> In porting lame but useful software, I often have to roll up my own
> distfile because upstream doesn't bother ever releasing their code.  I
> stick the distfiles in ~/public_distfiles so it gets the
> load-distribution love, but it seems that none of the mirrors updates
> from there very frequently -- I usually end up not getting the file to
> fetch until the next day.  If I commit my port update before it gets
> distributed, I usually get email complaints from users that day.
>=20
> Would it be possible for a single mirror that is in MASTER_SITE_LOCAL to
> sync local-distfiles more frequently, so that porters can commit
> local-distfile ports quicker after rolling them?

Given the asynchronous nature of the mirror updates, this is not a
trivial issue to solve, and has been on my mind before.  There are no
less than three steps required before the files show up on an ftp mirror.
First, you place the file in public_distfiles on freefall.  From there,
it has to be replicated to ftp-master(|.us|.eu).  Finally, the mirrors
have to pick it up from there.  For ftp.freebsd.org, I can promise that
the last step is done within hours (unless a very large dataset was just
uploaded to ftp-master).  Unless these files are made available directly
=66rom freefall, adding even more traffic load to it, I don't really see
that this delay can be brought down even more and will always be several
hours.  My conclusion so far as been that the best way is to put the
file in public_distfiles the day before the commit.

Best,
-erwin


--=20
Erwin Lansing                                     http://droso.org
Security is like an onion.          (o_ _o)
It's made up of several layers   \\\_\   /_///    erwin@FreeBSD.org
And it makes you cry.            <____) (____>    erwin@aauug.dk

--DWg365Y4B18r8evw
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)

iD8DBQFHC/ndqy9aWxUlaZARAhtdAJ4watYy1H7ZTr+UHcJwL8xwQZb7nwCg/LB3
gTKp2emiUSTljA4O/93aF30=
=xbqW
-----END PGP SIGNATURE-----

--DWg365Y4B18r8evw--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071009215957.GZ73011>