> On 10:30 Mon 15 May , Matias Grana wrote: > > hi; > > Beginning a week ago or so, I can't emerge --sync anymore. It always > > quits with a timeout error. Like this: > > > > receiving file list ... > > 143979 files to consider > > rsync error: timeout in data send/receive (code 30) at io.c(171) > > [sender=2.6.8] > > rsync: connection unexpectedly closed (3358508 bytes received so far) > > [receiver] > > rsync error: error in rsync protocol data stream (code 12) at io.c(463) > > [receiver=2.6.8] > > rsync: connection unexpectedly closed (3358508 bytes received so far) > > [generator] > > rsync error: error in rsync protocol data stream (code 12) at io.c(463) > > [generator=2.6.8] > > >>> retry ...
On Mon, May 15, 2006 at 03:37:54PM +0100, Neil Bothwick wrote: > Try a different rsync server. > -- > Neil Bothwick On Mon, May 15, 2006 at 11:19:36AM -0300, Pablo Antonio wrote: > I'm pretty likely not the best person to help you out but, I'm > wondering... Have you tried with any other mirror? Does it still happen? I tried with SYNC="rsync://rsync.gentoo.org/gentoo-portage" SYNC="rsync://rsync.samerica.gentoo.org/gentoo-portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" with no luck. If it's just a matter of non-permanent congestion, I can live with emerge-webrsync. Anyway, I was wondering whether there was a different approach. By the way, Pablo: it seems that we are very close to each other. Which mirror do you use? Thanks, Matias -- [email protected] mailing list
