|
|

楼主 |
发表于 2008-2-16 18:11:39
|
显示全部楼层
Have deleted all mirror and rsync address, rebooted, and emerge --sync again,
but still use the old settings .....
# emerge --sync
>>> Starting rsync with rsync://134.68.220.97/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
>>> Retrying...
>>> Starting retry 1 of 3 with rsync://134.68.220.73/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
>>> Retrying...
>>> Starting retry 2 of 3 with rsync://64.127.121.98/gentoo-portage
>>> Checking server timestamp ...
Welcome to owl.gentoo.org
Server Address : 64.127.121.98
Contact Name : mirror-admin@gentoo.org
Hardware : 4 x Intel(R) Xeon(TM) CPU 2.40GHz, 1024MB RAM
Please note: common gentoo-netiquette says you should not sync more
than once a day. Users who abuse the rsync.gentoo.org rotation
may be added to a temporary ban list.
MOTD brought to you by motd-o-matic, version 0.3
receiving file list ... done
timed out
timestamp.chk
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [generator=2.6.9]
rsync error: received SIGUSR1 (code 19) at main.c(1185) [receiver=2.6.9]
>>> Retrying...
>>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9]
!!! Rsync has not successfully finished. It is recommended that you keep
!!! trying or that you use the 'emerge-webrsync' option if you are unable
!!! to use rsync due to firewall or other restrictions. This should be a
!!! temporary problem unless complications exist with your network
!!! (and possibly your system's filesystem) configuration. |
|