Can you reproduce by manually curling it? On Sun, Aug 2, 2020, 18:41 Dale <rdalek1...@gmail.com> wrote:
> Howdy, > > I was in the middle of a update and noticed the server I was connected to > was really slow. I edited make.conf and removed that server. I then > restarted emerge so it would try the next server and hopefully be a better > speed. When I used tail to monitor emerge-fetch.log, it wasn't updating > the fetch progress. It stopped right where I stopped the previous > attempt. It looks like this: > > > root@fireball / # tail -f /var/log/emerge-fetch.log > 166050K .......... .......... .......... .......... .......... 29% 66.1K > 59m17s > 166100K .......... .......... .......... .......... .......... 29% 81.6K > 59m17s > 166150K .......... .......... .......... .......... .......... 29% 76.2K > 59m17s > 166200K .......... .......... .......... .......... .......... 29% 63.7K > 59m17s > 166250K .......... .......... .......... .......... .......... 29% 29.3K > 59m19s > 166300K .......... .......... .......... .......... .......... 29% 31.7K > 59m22s > 166350K .......... .......... .......... .......... .......... 29% 44.7K > 59m23s > 166400K .......... .......... .......... .......... .......... 29% 73.7K > 59m23s > 166450K .......... .......... .......... .......... .......... 29% 22.6K > 59m27s > 166500K .......... .......... .......... .^C > > > > It should show it connecting to the next server and resuming the download > but it doesn't. I see the network activity on gkrellm but nothing in the > log. It is downloading tho. Gkrellm shows it is better but why is the log > not showing that? > > Is this a bug or am I missing something? It use some other file on > retries or something? > > Thanks. > > Dale > > :-) :-) >
