Date: Wed, 27 Oct 2004 15:46:36 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: John Hay <jhay@icomtek.csir.co.za> Cc: freebsd-ports@freebsd.org Subject: Re: please test: Secure ports tree updating Message-ID: <xzpwtxcgtoj.fsf@dwp.des.no> In-Reply-To: <20041027124704.GA12880@zibbi.icomtek.csir.co.za> (John Hay's message of "Wed, 27 Oct 2004 14:47:04 %2B0200") References: <417EAC7E.2040103@wadham.ox.ac.uk> <xzp654wiffv.fsf@dwp.des.no> <20041027124704.GA12880@zibbi.icomtek.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
John Hay <jhay@icomtek.csir.co.za> writes: > On Wed, Oct 27, 2004 at 01:11:16PM +0200, Dag-Erling Sm?rgrav wrote: > > Colin Percival <colin.percival@wadham.ox.ac.uk> writes: > > > CVSup is slow, insecure, and a memory hog. > > if cvsup is slow, you're not using it right. > Well it is fast on our local links but on a long delay link, like what > we have from here in SA to USA, it is pretty slow. With rsync from > ftp-master, ftp-master.us and ftp-master.eu I can get 100-150kByte/s, > but with cvsup (with the -s option) I can only get about 30kByte/s. It > is less of a memory hog than rsync on the server side though. you must be doing something wrong. cvsup was designed to work well on high-latency links. are you running it with -s? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpwtxcgtoj.fsf>