On Wed, Mar 19, 2014 at 8:47 AM, Giuseppe Scrivano <[email protected]> wrote: > Darshit Shah <[email protected]> writes: > >> I was trying to download a large ISO (>4GB) through a metalink file. >> >> The first thing that struck me was: The file is first downloaded to >> /tmp and then moved to the location. >> >> Is there any specific reason for this? I understand that downloading >> partial files to /tmp , stitching them and then moving them to the >> actual download location might be good on I/O. But, a very popular >> case in such scenarios is when /tmp is not large enough to store the >> file, but I have enough capacity in the location where I'm trying to >> store it. > > I am not familiar with the metalink code as well and I don't know if > there is any better reason for this behaviour, but if the reason is only > because of an optimization then we shouldn't do this. > Yeah, I agree. This part needs changing. Also, we need to test the stability of Wget. Can't have it segfaulting on every failure.
The progress output is very complex and unreadable too. I think I'll make a Wiki page based on all the things that need changing in parallel-wget. -- Thanking You, Darshit Shah
