| 1 |
Mick wrote: |
| 2 |
> I have noticed this phenomenon which I am not sure I can explain very |
| 3 |
> satisfactorily. Just after midnight (GMT) any attempt to resync proves |
| 4 |
> futile: |
| 5 |
> ========================================================== |
| 6 |
> # eix-sync |
| 7 |
> * Running emerge --sync |
| 8 |
> |
| 9 |
>>>> Starting rsync with rsync://88.156.78.16/gentoo-portage... |
| 10 |
>>>> rsync error: received SIGUSR1 (code 19) at main.c(1286) [receiver=3.0.4] |
| 11 |
>>>> |
| 12 |
<snip> |
| 13 |
>>>> Starting retry 1 of 3 with rsync://137.226.34.228/gentoo-portage |
| 14 |
>>>> |
| 15 |
>>>> |
| 16 |
> Checking server timestamp ...Welcome to rsync.informatik.rwth-aachen.de (137.226.34.228). |
| 17 |
> |
| 18 |
<snip> |
| 19 |
> An hour or so later resync'ing happens without any problem. Why is this? |
| 20 |
> |
| 21 |
When it works the second time, is it the same server? rsync.gentoo.org |
| 22 |
and rsync.$CONTINENT.gentoo.org are just cnames pointing to servers so |
| 23 |
you could be getting different hosts via dns round robin. This is |
| 24 |
evidenced by the two different ips in your post. |
Archives