cvsup takes too long?

[Frank Shute]

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 hours to
> > >>complete.  Is this normal behaviour?
> > >
> > >No.  I find the .uk cvsup servers a little unreliable though. 
> > >
> > >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, even 
> > at 3am, I now use cvsup.uk.freebsd.org and it is all done in a few minutes. 
> 
> 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 saying
> "Access Limit Exceeded"!
> 
> I am now looking into portsnap.  The man page seems to me a bit vague for the
> first read unfortunately :-(
> 
> 

There's a bit about it in the handbook:

http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/portsnap.html


-- 

 Frank 


echo "f r a n k @ e s p e r a n c e - l i n u x . c o . u k" | sed 's/ //g'

                      --->PGP keyID: 0x10BD6F4B<---