I have noticed this phenomenon which I am not sure I can explain very satisfactorily. Just after midnight (GMT) any attempt to resync proves futile: ========================================================== # eix-sync * Running emerge --sync >>> Starting rsync with rsync://88.156.78.16/gentoo-portage... >>> Checking server timestamp ...
contact: f...@vectranet.pl receiving incremental file list timestamp.chk timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(541) [generator=3.0.4] >>> Retrying... rsync error: received SIGUSR1 (code 19) at main.c(1286) [receiver=3.0.4] >>> Starting retry 1 of 3 with rsync://137.226.34.228/gentoo-portage >>> Checking server timestamp ... Welcome to rsync.informatik.rwth-aachen.de (137.226.34.228). This server is part of the SunSITE Central Europe and is located in Aachen, Germany (http://sunsite.informatik.rwth-aachen.de). receiving incremental file list timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(541) [generator=3.0.4] >>> Retrying... [snip...] ========================================================== An hour or so later resync'ing happens without any problem. Why is this? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
