Deluge 1.3.14 (same "issue" with 1.3.13 though)
OS: Windows 10 x64
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.
Support forum for Deluge on Microsoft Windows OS
3 posts • Page 1 of 1
- Top Bloke
- Posts: 3280
- Joined: Mon Dec 07, 2009 6:04 am
- OS or Distro: Ubuntu 16.04
- Location: Scotland
It is libtorrent related and it's called 'mutable torrents' BEP 38. It is mentioned in lt 1.1.x changelog so you could test that version. Remember your torrents will also need to follow the BEP 38 specs.
Who is online
Users browsing this forum: No registered users and 2 guests