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. Wget tried to download the file to /tmp, where it failed since it ran out of free space. As a result, Wget crashed instead of exiting gracefully. Failing in itself should be considered a bug since I never intended to save it to /tmp. The download location I selected has enough disk space. We know that origin/master does not fail even with very large files. Even if the disk is out of capacity, Wget manages to exit gracefully. I'll try to dive into the code once I get time, but if anyone has any ideas in the meantime, it would be greatly appreciated! -- Thanking You, Darshit Shah
