How does last_activity work? #743
-
Let's say I have a share_limit group with the following options: max_ratio: 10.0
max_seeding_time: 2w
min_seeding_time: 24h
last_active: 2d I noticed that a torrent has been seeding for one week, has reached a ratio of 1.1, but has had no activity in the last 48 hours (the "LastActiveLimitNotReached" tag has been removed). Does this mean the torrent cannot be removed until it reaches either the maximum ratio or the maximum seeding time? If so, what is the correct use case for last_active? Ideally, I was hoping that torrents with no activity for more than 48 hours would be removed, but only if they had been seeded for at least 24 hours. The maximum seeding time, in any case, is two weeks or reaching a ratio of 10.0. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Please read the wiki instead of guessing at what attributes do. Last Active prevents removals. |
Beta Was this translation helpful? Give feedback.
-
I’ve read the wiki several times, but I might still be misunderstanding something. My confusion stemmed from the assumption that last_active would function similarly to qBittorrent’s Limit Share Ratio Inactivity setting—meaning that if a torrent hasn’t been active for the last X minutes, it would be paused or marked as complete, just like when the seed time or seed ratio is reached. Your clarification that last_active prevents removals cleared up my misunderstanding and helped me realize that it works differently. As long as the last_active threshold has not been exceeded, torrents will not be removed, even if the seed ratio and/or seed time have been reached. I hope we can update the documentation to help future users avoid confusing qBittorrent’s Limit Share Ratio Inactivity setting with qbit_manage’s last_active setting and that they work in fundamentally different ways. |
Beta Was this translation helpful? Give feedback.
Please read the wiki instead of guessing at what attributes do.
Last Active prevents removals.