cvsup takes too long?
ceri at submonkey.net
Wed Nov 29 10:12:52 GMT 2006
Content-Type: text/plain; charset=us-ascii
On Tue, Nov 28, 2006 at 10:33:44PM +0000, Progga wrote:
> On Tue, Nov 28, 2006 at 08:46:11PM +0000, martin at rakupottery.org.uk wrote:
> > >On Tue, Nov 28, 2006 at 05:24:59PM +0000, Progga wrote:
> > >>
> > >>I was updating the ports collection inside a jail using CVSUP
> > >>(cvsup2.uk.freebsd.org) 2/3 days ago and it took well over eight hour=
> > >>complete. Is this normal behaviour?
> > >
> > >No. I find the .uk cvsup servers a little unreliable though.=20
> > >
> > >Either way, I expect that you'll find portsnap is better if you don't
> > >need an actual CVS ports tree.
> > I stopped using cvsup2 some months ago as it had become terribly slow, =
> > at 3am, I now use cvsup.uk.freebsd.org and it is all done in a few minu=
> Thanks all for the replies.
> According to fastest_cvsup:
> - 1st: cvsup3.uk.freebsd.org 12.58 ms
> - 2st: cvsup4.uk.freebsd.org 14.63 ms
> - 3st: cvsup2.uk.freebsd.org 15.98 ms
> I have updated again; cvsup3 was really fast and cvsup2 refused access sa=
> "Access Limit Exceeded"!
> I am now looking into portsnap. The man page seems to me a bit vague for=
> first read unfortunately :-(
# portsnap fetch extract
# portsnap fetch update
Runs from cron:
53 2 * * */3 /usr/sbin/portsnap cron update
That must be wonderful! I don't understand it at all.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
-----END PGP SIGNATURE-----
More information about the Ukfreebsd