* [gentoo-user] what's wrong with rsync 3.0.6?
@ 2010-03-13 19:15 99% Jarry
0 siblings, 0 replies; 1+ results
From: Jarry @ 2010-03-13 19:15 UTC (permalink / raw
To: gentoo-user
Hi, I noticed this error when I try to sync my portage tree:
---------------
obelix ~ # emerge --sync
>>> Starting rsync 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(544) [receiver=3.0.6]
>>> Retrying...
>>> Starting retry 1 of 3 with rsync://134.68.220.74/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544) [receiver=3.0.6]
>>> Retrying...
---------------
It started about month ago and it happens quite frequently, I'd say
there is ~30% chance I get this message when I try "emerge --sync".
What could be the reason for this, and how could I fix it?
Jarry
--
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2010-03-13 19:15 99% [gentoo-user] what's wrong with rsync 3.0.6? Jarry
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox