![]() Registered Member ![]()
|
I'm running ktorrent 2.2.2 on KDE 3.5.7 on Debian Lenny.
Mostly, I'm very happy so far (after years of bittornado, the slick one-window interface, with minimize-to-taskbar, is sweet!) Also, I love the idea of the queue management, where I can set my max share ratio (currently 2.72) and max seed time (currently 48 hours) and just forget all about my torrents once they're downloaded. I do, of course, have "Keep seeding after download is finished" ticked. The problem is it doesn't seem to actually work. I have one upload with a Time Seeded of "2 days 09:14:45" and another one with a share ratio of 2.73, and they're both still seeding merrily away. Shouldn't they be stopped (and preferably deleted right out of the queue)? Note that when I open the QM, all of these uploads show as controlled by Queue Manager. |
![]() Registered Member ![]()
|
|
![]() Moderator ![]()
|
|
![]() Registered Member ![]()
|
Yup, as I mentioned in my post, I had both of those values set in the Preferences.
Okay, weird... I stopped and removed those torrents manually, and now it seems to work fine... Maybe changing those limits doesn't take effect on torrents that are already seeding when you make the change...? Anyway, my most recent torrent has done exactly what it should... seeded up to my specified Share Ratio (currently 3.00), and kicked over to "seeding completed" and shows in QM as user controlled, just like you say. But I swear, it was acting funny! ![]() Thanks for the prompt feedback, anyway! ![]() |
![]() Registered Member ![]()
|
I have noticed this too. Your later post mentioned perhaps it was only because you set the limits while seeding and I have to agree. Stopping the torrent while seeding/leeching, then setting the limits and restarting is needed to get the limits to set properly otherwise they do seem to keep right on going forever. Not that overseeding is a bad thing... We could all benefit from extra seeding and do a little ourselves but yeah, I have noticed this as well. Glad to hear you have a one down three up share policy, that is what I set mine at. |
![]() Moderator ![]()
|
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]