Bug 273947 - Add option to stop seeding or move on while seeding after download is complete
Summary: Add option to stop seeding or move on while seeding after download is complete
Status: REPORTED
Alias: None
Product: kget
Classification: Applications
Component: torrent (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-23 10:51 UTC by Ray Rashif
Modified: 2014-09-17 02:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ray Rashif 2011-05-23 10:51:55 UTC
Version:           unspecified (using KDE 4.6.3) 
OS:                Linux

Currently a torrent download will continue to download (seed) after it has completed (leeching).

This is problematic if there is a queue, especially a queue of 1.

Reproducible: Always

Steps to Reproduce:
1. Download torrent
2. Open torrent with kget
3. Set download queue to 1
4. Download something else

Actual Results:  
Download does not move on to the next in queue (if within the limit set) when the torrent has completed leeching but is still seeding.

Expected Results:  
Download stops seeding and continues on to the next download in the list, or continues seeding but starts the next download once the leeching has completed (in this case a "number of seeds" queue may be necessary).

While ktorrent exists for advanced functionality, the feature described herein is fundamental to downloading torrents and should be available in a basic torrent client.
Comment 1 Ryan K 2014-09-17 02:51:56 UTC
+1 for this feature; I get the same behavior in KDE 4.14.3.

It's impossible to download a queue of torrents if you have the "Maximum transfers per group" set because, as far as kget is concerned, a torrent never "finishes", it just starts seeding.

I'd suggest that once finished, the next download in the queue is automatically started (while the finished torrent begins seeding). As the OP said, perhaps a separate limit for the number of seeds per group would be helpful too.