I launched a wget job with the following command:urls=(https://example.com/file1 https://example.com/file2      https://example.com/file3 https://example.com/file4)for url in ${urls[@]}; do   wget $url 2>/dev/null && echo $url done >> progress & doneThese were files of ~30-40G each so I let it run overnight. I checked again today and found the following:-rw-rw-r-- 1 a staff  13M Mar 18 15:11 file1-rw-rw-r-- 1 a staff  18M Mar 18 15:12 file1.1-rw-rw-r-- 1 a staff  38G Mar 18 21:10 file1.2-rw-rw-r-- 1 a staff  12M Mar 18 15:12 file2-rw-rw-r-- 1 a staff  44G Mar 18 21:35 file2.1-rw-rw-r-- 1 a staff  446 Mar 18 21:35 progress-rw-rw-r-- 1 a staff  40G Mar 18 21:24 file3.1-rw-rw-r-- 1 a staff 4.4M Mar 18 15:12 file3-rw-rw-r-- 1 a staff 6.5M Mar 18 15:12 file4-rw-rw-r-- 1 a staff  42G Mar 18 21:27 file4.1In other words, I see a few filename.N files, which look like they might be the right size, but the filename files themselves are clearly too small. The progress file reports that all files were downloaded successfully:https://example.com/file1 done https://example.com/file2 done https://example.com/file3 done https://example.com/file4 done I have asked the person who made these available to me to provide me with md5sums of each file so I can see if any of the filename.N files are actually full copies. In the meantime, can I safely assume that the filename.N with the greatest value of N is actually a complete copy of the file in question? I am guessing that the wget process was restarted a few times and that's why I have the .N files but given that the && echo seems to have worked, does that mean that the files were indeed, eventually, downloaded correctly or could the && have been executed even for an incomplete download? 
Can I trust wget's exit status even if it was restarted?
wget