On Friday 16 January 2004 01:07 pm, gabriel wrote: > at the risk of being blasted by those who already know about this problem, > i have to ask: is there *still* something wrong with the rsync system? i > checked (bugs|forums|www).gentoo.org and there's nothing there about it, > but here's what i've got > > # emerge sync > > >>> starting rsync with rsync://128.227.163.19/gentoo-portage... > >>> checking server timestamp ... > > rsync: failed to connect to 128.227.163.19: Connection timed out > rsync error: error in socket IO (code 10) at clientserver.c(88) > > >>> retry ... > >>> > >>> > >>> Starting retry 1 of 3 with rsync://129.79.6.12/gentoo-portage > >>> checking server timestamp ... > > rsync: failed to connect to 129.79.6.12: Connection timed out > rsync error: error in socket IO (code 10) at clientserver.c(88) > > >>> retry ... > >>> > >>> > >>> Starting retry 2 of 3 with rsync://129.89.70.108/gentoo-portage > >>> checking server timestamp ... > > rsync: failed to connect to 129.89.70.108: Connection timed out > rsync error: error in socket IO (code 10) at clientserver.c(88) > > >>> retry ... > >>> > >>> > >>> Starting retry 3 of 3 with rsync://130.207.108.135/gentoo-portage > >>> checking server timestamp ... > > rsync: failed to connect to 130.207.108.135: Connection timed out > rsync error: error in socket IO (code 10) at clientserver.c(88) > > > could this be a firewall issue? i'm on a corporate lan, so i don't have > any real power over the firewall, but i'm not sure what could be the > problem if it's just me.
try selecting a dif mirror using mirrorselect a few of the mirrors dont seem to be responding -- Chris -- [EMAIL PROTECTED] mailing list
