Deluge
Split from: Queue Settings FAQ?
I have been wondering why my torrents NEVER stopped Seeding even though I set the "Stop Seeding Ratio" to "3" and now I know... the options do NOT stop the seeding!
So, how may I actually automatically stop a torrent from seeding upon reaching a ratio of, say, "3.00"?
NOTE: My torrent did NOT stop seeding even after reaching the ratio of "3", which I set to.
Stop seeding ratio ignored
Re: Queue Settings FAQ?
Same problem as lifestyle. I am not sure how to actually let Deluge stop/remove torrents that have met the criteria. So I have them configured but I still see torrents continuing to see even after 3.00 ratio.
Re: Stop seeding ratio ignored
I think there will be an issue simply stopping (pausing) the torrent at ratio because libtorrent will resume paused auto-managed torrents. The fix for this would be to pause and also disable auto-managed when it hits the ratio.
The not removing issue is strange, can you verify that the actual torrents have the 'remove at ratio' setting enabled rather than just the global setting?
What version of libtorrent are you using?
The not removing issue is strange, can you verify that the actual torrents have the 'remove at ratio' setting enabled rather than just the global setting?
What version of libtorrent are you using?
Re: Stop seeding ratio ignored
Hello, same problem here.
To be more precise it worked as expected, but broke after updating deluge. I'm using the git version (1.3.900-dev), updated to newest commit (2a3eb7b70cb5a71c741ffe105b51ee17cec11589), previously had some older git version from January, sorry I can't be more specific. I'm running Windows 7 (x64), python 2.7 (32bit), libtorrent 0.16.8.0, deluge from git (1.3.900-dev).
I've actually realized the problem when deluge sometimes ignored 'move completed' dir in addition to the 'stop at ratio' setting. I'm running deluge in daemon mode, running the gtkGUI while the torrents are seeded seems to fix the issue. Also, if I enter the gtkGUI, long after the torrents ratio has been reached (like set to stop at 2, but seeded over 4), deluge seems to check the 'stop at ratio' option and pauses the torrents the moment GUI is run (the ratio having been reached approximately an hour ago).
To sum it up, it's like daemon running alone doesn't trigger the checks required for certain options to work. Running the GUI, even if it's not focused, seems to properly trigger the checks.
I'll prepare log files when I have more time. For now mcored and lifestyle, could you check if running the GUI constantly (in background, but not minimized) fixes this for you? If yes, we'll know we're having the same issue and can file a more helpful bug report
UPDATE: Seems the move completed was an error on my end, sorry about that.
Got some time, so I've filed a bug report, take a look mcored and lifestyle, maybe you can contribute. http://dev.deluge-torrent.org/ticket/2291
To be more precise it worked as expected, but broke after updating deluge. I'm using the git version (1.3.900-dev), updated to newest commit (2a3eb7b70cb5a71c741ffe105b51ee17cec11589), previously had some older git version from January, sorry I can't be more specific. I'm running Windows 7 (x64), python 2.7 (32bit), libtorrent 0.16.8.0, deluge from git (1.3.900-dev).
I've actually realized the problem when deluge sometimes ignored 'move completed' dir in addition to the 'stop at ratio' setting. I'm running deluge in daemon mode, running the gtkGUI while the torrents are seeded seems to fix the issue. Also, if I enter the gtkGUI, long after the torrents ratio has been reached (like set to stop at 2, but seeded over 4), deluge seems to check the 'stop at ratio' option and pauses the torrents the moment GUI is run (the ratio having been reached approximately an hour ago).
To sum it up, it's like daemon running alone doesn't trigger the checks required for certain options to work. Running the GUI, even if it's not focused, seems to properly trigger the checks.
I'll prepare log files when I have more time. For now mcored and lifestyle, could you check if running the GUI constantly (in background, but not minimized) fixes this for you? If yes, we'll know we're having the same issue and can file a more helpful bug report
UPDATE: Seems the move completed was an error on my end, sorry about that.
Got some time, so I've filed a bug report, take a look mcored and lifestyle, maybe you can contribute. http://dev.deluge-torrent.org/ticket/2291