Transmission

Why try to "fix" this at the .resume level at all? Why not just replace most of loadProgress() with a simple for loop that sets all of the pieces' mtimes to the current time or something?
As you can see in the source code, loadProgress() actually sets all of the pieces' timeChecked to a same time ...

It seems like it generating the .resume files by hand is a lot more work than, say, going into resume.c and adding a line or two to make libtransmission think that all pieces have an up-to-date timestamp...
I have read the loadProgress() and saveProgress() code. It seems that if the time-checked ...

I found that I had read the saveProgress() before and I don't think it's the point.
Actually I really wonder how this trick could work in the previous version. Yes, I build the .resume file and move it into the right directory, but the session don't read the .resume file for checking duplicated ...

Thanks Jordan. I'll take a look at it and hope I can understand...
The reason why I need this trick is that I write a seed robot and it uploads a lot of new torrents to a tracker frequently. Some of the files are really huge, and the verifying progress will slow down the machine.

Firstly, in the previous 2.1x version of Transmission, I found a trick to do this. I just wrote a script to build a .resume file corresponding to the torrent I wanted to add *BEFORE* I really added it to Transmission and moved that .resume file to the directory where it should be. The .resume file I ...