[Feature Request] Delete torrent when time active is > 00:00:00 #3689

Closed
opened 2026-02-21 16:54:39 -05:00 by deekerman · 15 comments
Owner

Originally created by @dannyhanes on GitHub (Jan 7, 2016).

Right now we can automatically delete a torrent when it reaches a certain ratio, but that means any torrent that isn't being snatched up will just be left behind. Time active is what I am looking for, but really we should have a dropdown of options. I would like have it say...

Seed torrent until their ratio reaches then
[or]
Seed torrent until their

This way if it isn't a very active torrent, but has been in our queue for quite a while, we can purge it out.

Originally created by @dannyhanes on GitHub (Jan 7, 2016). Right now we can automatically delete a torrent when it reaches a certain ratio, but that means any torrent that isn't being snatched up will just be left behind. Time active is what I am looking for, but really we should have a dropdown of options. I would like have it say... Seed torrent until their ratio reaches <ratio> then <action> [or] Seed torrent until their <time active> is greater than 00:00:00 This way if it isn't a very active torrent, but has been in our queue for quite a while, we can purge it out.
Author
Owner

@Snurre86 commented on GitHub (Jan 7, 2016):

like it, related to #4353

@Snurre86 commented on GitHub (Jan 7, 2016): like it, related to #4353
Author
Owner

@Snurre86 commented on GitHub (Jan 7, 2016):

Are you talking about a torrent that will not seed to anyone for days or it will not download at all for days?

@Snurre86 commented on GitHub (Jan 7, 2016): Are you talking about a torrent that will not seed to anyone for days or it will not download at all for days?
Author
Owner

@dannyhanes commented on GitHub (Jan 7, 2016):

Here is the use case.

Some of the sites I use require us to seed to a given ratio OR seed for a given duration. So in the even that I have a torrent that just stays at a ratio of 0.0...after the two week requirement, I can delete it out despite not having a positive ratio.

I will typically go into qBitorrent and sort by "Time Active" and delete all those that have an active time greater than 2 weeks.

Does that make more sense?

@dannyhanes commented on GitHub (Jan 7, 2016): Here is the use case. Some of the sites I use require us to seed to a given ratio OR seed for a given duration. So in the even that I have a torrent that just stays at a ratio of 0.0...after the two week requirement, I can delete it out despite not having a positive ratio. I will typically go into qBitorrent and sort by "Time Active" and delete all those that have an active time greater than 2 weeks. Does that make more sense?
Author
Owner

@Snurre86 commented on GitHub (Jan 7, 2016):

so like say:
fe25c12c-a4a3-11e5-849e-70a99b0735dd

@Snurre86 commented on GitHub (Jan 7, 2016): so like say: ![fe25c12c-a4a3-11e5-849e-70a99b0735dd](https://cloud.githubusercontent.com/assets/7798635/12179043/0d84228a-b575-11e5-9f3a-109528a9faf9.png)
Author
Owner

@Snurre86 commented on GitHub (Jan 7, 2016):

The wording is not to good as it is actively seeding or downloading just noting happens ...

Maybe
fe25c12c-a4a3-11e5-849e-70a99b0735dd

@Snurre86 commented on GitHub (Jan 7, 2016): The wording is not to good as it is actively seeding or downloading just noting happens ... Maybe ![fe25c12c-a4a3-11e5-849e-70a99b0735dd](https://cloud.githubusercontent.com/assets/7798635/12179468/5e55227a-b577-11e5-8d11-551fd4195b4f.png)
Author
Owner

@dannyhanes commented on GitHub (Jan 7, 2016):

I like that. What would happen if I set the following:

[x] Seed torrents until their ratio reaches <0,0> then
[x] Count from when torrent reaches completed status
[ ] Continue seeding it less than <0> active seeds
[x] Remove torrent if inactive for <30> days and <0> hours

I worry that the 0,0 would remove them immediately. I don't care what the ratio is, I care more about the active time.

@dannyhanes commented on GitHub (Jan 7, 2016): I like that. What would happen if I set the following: [x] Seed torrents until their ratio reaches <0,0> then <remove them> [x] Count from when torrent reaches completed status [ ] Continue seeding it less than <0> active seeds [x] Remove torrent if inactive for <30> days and <0> hours I worry that the 0,0 would remove them immediately. I don't care what the ratio is, I care more about the active time.
Author
Owner

@Snurre86 commented on GitHub (Jan 7, 2016):

if you set it to 0 it would be the same as disabling it so "Count from when torrent reaches completed status" would also be disabled i guess. Why don't you care about the ratio?

@Snurre86 commented on GitHub (Jan 7, 2016): if you set it to 0 it would be the same as disabling it so "Count from when torrent reaches completed status" would also be disabled i guess. Why don't you care about the ratio?
Author
Owner

@dannyhanes commented on GitHub (Jan 7, 2016):

Because after two weeks, or 6 months... I want the torrent removed. I don't care if the ratio is 0 or 10. I only want it active for a specific amount of time.

@dannyhanes commented on GitHub (Jan 7, 2016): Because after two weeks, or 6 months... I want the torrent removed. I don't care if the ratio is 0 or 10. I only want it active for a specific amount of time.
Author
Owner

@naikel commented on GitHub (Jan 7, 2016):

I already submitted a PR for this. It only needs to be merged: #4266

@naikel commented on GitHub (Jan 7, 2016): I already submitted a PR for this. It only needs to be merged: #4266
Author
Owner

@Snurre86 commented on GitHub (Jan 7, 2016):

I like the wording "seed time" but how many minutes are there in tree weeks?

Could we have days, hours and minutes?

@Snurre86 commented on GitHub (Jan 7, 2016): I like the wording "seed time" but how many minutes are there in tree weeks? Could we have days, hours and minutes?
Author
Owner

@naikel commented on GitHub (Jan 7, 2016):

You do the math and that's it! The feature allows big numbers. The max is 525600 which is a year (365 * 24 * 60).

I have it working since last October in my own version of qBittorrent. I have a global set time of 1440 minutes and then the torrents are paused (you can select delete of course). So all my torrents are seeded for 15 days max.

You can also choose a combination. For example seed ratio max of 2 and 15 days. Whatever comes first it will stop (or delete) the torrent. It's really useful and works pretty well.

@naikel commented on GitHub (Jan 7, 2016): You do the math and that's it! The feature allows big numbers. The max is 525600 which is a year (365 \* 24 \* 60). I have it working since last October in my own version of qBittorrent. I have a global set time of 1440 minutes and then the torrents are paused (you can select delete of course). So all my torrents are seeded for 15 days max. You can also choose a combination. For example seed ratio max of 2 and 15 days. Whatever comes first it will stop (or delete) the torrent. It's really useful and works pretty well.
Author
Owner

@Snurre86 commented on GitHub (Jan 7, 2016):

I am a little under the weather so my brain is not that sharp, but here is another suggestion

fe25c12c-a4a3-11e5-849e-70a99b0735dd

@Snurre86 commented on GitHub (Jan 7, 2016): I am a little under the weather so my brain is not that sharp, but here is another suggestion ![fe25c12c-a4a3-11e5-849e-70a99b0735dd](https://cloud.githubusercontent.com/assets/7798635/12185714/11134f52-b59d-11e5-83b0-89c034db178c.png)
Author
Owner

@dannyhanes commented on GitHub (Jan 8, 2016):

Yeah that looks better. This would help me automatically keep my torrents purged after a set time.

@dannyhanes commented on GitHub (Jan 8, 2016): Yeah that looks better. This would help me automatically keep my torrents purged after a set time.
Author
Owner

@ghost commented on GitHub (Mar 20, 2017):

@naikel - I looked over #4266 . Great job with what you've done. Hopefully it will make it into the next release.

@ghost commented on GitHub (Mar 20, 2017): @naikel - I looked over #4266 . Great job with what you've done. Hopefully it will make it into the next release.
Author
Owner

@zeule commented on GitHub (Mar 22, 2017):

Closing as duplicate of #1646.

@zeule commented on GitHub (Mar 22, 2017): Closing as duplicate of #1646.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#3689
No description provided.