[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-wget] [bug #54828] wget stalled download shows wrong speed per seco

From: Darshit Shah
Subject: [Bug-wget] [bug #54828] wget stalled download shows wrong speed per second
Date: Fri, 12 Oct 2018 08:31:24 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Update of bug #54828 (project wget):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Closed                 


Follow-up Comment #1:

This is actually two different issues.

Anyways, firstly, the speed being stuck is a technical limitation of Wget
being a single threaded application. Wget uses only blocking network sockets
and while it is blocked on a read() call, there is nothing it can do to update
the UI. Similarly, mentioning that it is stalled is also not possible without
adding threading support. Something that we do not intend to do. These issues
don't exist in Wget2 which has been designed with multi-threading from the
very beginning.

Regarding the "(Success)" string, that is not controlled by Wget at all. It is
in fact the string reported by the kernel for the last error. In your case, it
seems to be that the last socket operation was a success, but the connection
was still terminated. 


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]