Posted August 04, 2015
If I abort the download (or it gets aborted due to internet problems etc.), and I later restart it, is there any reason to run verify or verify -delete before restarting the download?
I needed to restart the download (aborted it myself first) and decided to run verify -delete first so that it would delete the partial files that may be there, and also check for any other corrupted files (and delete them too). But it seemed to take so long time with this amount of files, so I aborted the verification and resumed with the download. At least it seemed to continue about at the same place where it aborted, showing around 720 GB remaining. I guess I'll run the verification afterwards.
What happens to those partial files that weren't finished, the download notices they are not ok, and just overwrites them? Or does it leave them be, thinking they are ok (until I will verify them myself)?
Ps. Overall the script is still running beautifully. The main feature requests I have are:
- The clean option like someone mentioned, e.g. that it lists and maybe moves orphan/obsolete files to another directory so I can check and decide if I want to keep them or delete them. Just in case GOG makes some stupid "update" like removing Outcast classic, or the DOS version of Earth 2140 from the extras...
- Proxy support. The internet at my workplace is like 6-7 times faster than my cable modem at home, sometimes that matters... :) I've been thinking of forking gogrepo and maybe trying if I can implement that myself to the current gogrepo.py, but I would be glad if the real python coding masters would do it instead, at least for the public version. I wouldn't probably want my amateur code to be included in the original. I could be a tester for that proxy support though, as I have means to test it obviously. (Well, actually starting this weekend, I will be abroad for four weeks, but before and after that.)
I needed to restart the download (aborted it myself first) and decided to run verify -delete first so that it would delete the partial files that may be there, and also check for any other corrupted files (and delete them too). But it seemed to take so long time with this amount of files, so I aborted the verification and resumed with the download. At least it seemed to continue about at the same place where it aborted, showing around 720 GB remaining. I guess I'll run the verification afterwards.
What happens to those partial files that weren't finished, the download notices they are not ok, and just overwrites them? Or does it leave them be, thinking they are ok (until I will verify them myself)?
Ps. Overall the script is still running beautifully. The main feature requests I have are:
- The clean option like someone mentioned, e.g. that it lists and maybe moves orphan/obsolete files to another directory so I can check and decide if I want to keep them or delete them. Just in case GOG makes some stupid "update" like removing Outcast classic, or the DOS version of Earth 2140 from the extras...
- Proxy support. The internet at my workplace is like 6-7 times faster than my cable modem at home, sometimes that matters... :) I've been thinking of forking gogrepo and maybe trying if I can implement that myself to the current gogrepo.py, but I would be glad if the real python coding masters would do it instead, at least for the public version. I wouldn't probably want my amateur code to be included in the original. I could be a tester for that proxy support though, as I have means to test it obviously. (Well, actually starting this weekend, I will be abroad for four weeks, but before and after that.)
Post edited August 04, 2015 by timppu