| 1 |
I have noticed this phenomenon which I am not sure I can explain very |
| 2 |
satisfactorily. Just after midnight (GMT) any attempt to resync proves |
| 3 |
futile: |
| 4 |
========================================================== |
| 5 |
# eix-sync |
| 6 |
* Running emerge --sync |
| 7 |
>>> Starting rsync with rsync://88.156.78.16/gentoo-portage... |
| 8 |
>>> Checking server timestamp ... |
| 9 |
|
| 10 |
contact: ftp@×××××××××.pl |
| 11 |
|
| 12 |
receiving incremental file list |
| 13 |
timestamp.chk |
| 14 |
timed out |
| 15 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(541) |
| 16 |
[generator=3.0.4] |
| 17 |
>>> Retrying... |
| 18 |
rsync error: received SIGUSR1 (code 19) at main.c(1286) [receiver=3.0.4] |
| 19 |
|
| 20 |
|
| 21 |
>>> Starting retry 1 of 3 with rsync://137.226.34.228/gentoo-portage |
| 22 |
>>> Checking server timestamp ... |
| 23 |
Welcome to rsync.informatik.rwth-aachen.de (137.226.34.228). |
| 24 |
This server is part of the SunSITE Central Europe and is located |
| 25 |
in Aachen, Germany (http://sunsite.informatik.rwth-aachen.de). |
| 26 |
|
| 27 |
receiving incremental file list |
| 28 |
timed out |
| 29 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(541) |
| 30 |
[generator=3.0.4] |
| 31 |
>>> Retrying... |
| 32 |
[snip...] |
| 33 |
========================================================== |
| 34 |
|
| 35 |
An hour or so later resync'ing happens without any problem. Why is this? |
| 36 |
-- |
| 37 |
Regards, |
| 38 |
Mick |
Archives