| 1 |
Am 14.03.2010 00:42, schrieb pk: |
| 2 |
> On 2010-03-13 20:15, Jarry wrote: |
| 3 |
> |
| 4 |
>> obelix ~ # emerge --sync |
| 5 |
>>>>> Starting rsync with rsync://134.68.220.73/gentoo-portage... |
| 6 |
>>>>> Checking server timestamp ... |
| 7 |
>> timed out |
| 8 |
>> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
| 9 |
>> rsync.c(544) [receiver=3.0.6] |
| 10 |
>>>>> Retrying... |
| 11 |
> |
| 12 |
> It's the server, not rsync that's at fault. rsync is merely telling you |
| 13 |
> that it cannot connect and is retrying to connect. Just choose another |
| 14 |
> mirror (emerge mirrorselect if you haven't already and then do |
| 15 |
> 'mirrorselect -i' - of course without the ''). |
| 16 |
> |
| 17 |
> Best regards |
| 18 |
> |
| 19 |
> Peter K |
| 20 |
> |
| 21 |
|
| 22 |
It can also happen if you are one a slow or lossy connection or have |
| 23 |
other network problems. I, for example, experienced similar problems |
| 24 |
when reverse DNS lookups did not work. |
| 25 |
|
| 26 |
In this case, you can try to set a longer timeout. For this, add |
| 27 |
PORTAGE_RSYNC_INITIAL_TIMEOUT=60 |
| 28 |
or something similar to /etc/make.conf |
| 29 |
|
| 30 |
Hope this helps, |
| 31 |
Florian Philipp |
Archives