Torrent hashes when added in queued state
Posted: Wed Mar 08, 2017 8:21 pm
Deluge 1.3.14 (same "issue" with 1.3.13 though)
LibTorrent 1.0.11.0
OS: Windows 10 x64
Plugins: ltConfig
Greetings,
I've got Deluge set up to only allow one torrent downloading at a time. This is to avoid files "colliding" since at times torrents containing the same files are added.
One thing I'm struggling with in this scenario is that if two torrents with the same files are added within a certain time span, the second torrent will start hash checking immediately even though it's still queued.
This causes the second torrent to start downloading a most of the files once it's removed even though they already exist.
How I expect it to work is that once the first torrent is finished the queued one will get active and start hashing and then immediately start seeding unless there's files that differ.
Is there any way around this issue? I'm guessing it's not considered a bug but rather a feature request.
Regards,
MH
LibTorrent 1.0.11.0
OS: Windows 10 x64
Plugins: ltConfig
Greetings,
I've got Deluge set up to only allow one torrent downloading at a time. This is to avoid files "colliding" since at times torrents containing the same files are added.
One thing I'm struggling with in this scenario is that if two torrents with the same files are added within a certain time span, the second torrent will start hash checking immediately even though it's still queued.
This causes the second torrent to start downloading a most of the files once it's removed even though they already exist.
How I expect it to work is that once the first torrent is finished the queued one will get active and start hashing and then immediately start seeding unless there's files that differ.
Is there any way around this issue? I'm guessing it's not considered a bug but rather a feature request.
Regards,
MH