"Seed Forever" option turning itself on

[yerfspd]

I have Transmission v1.21 (5890) running on OS X v10.5.2 Intel. Once a torrent finishes seeding to the global setting ratio it will stop like it's supposed to do. However, when I "resume all" of my list, the setting for seeding under Options in the Inspector (for all torrents at or above current global stop seeding ratio) sets itself to "seed forever" from "global setting". The main list still shows the download as paused and seeding complete but I'll often check the list and find something I haven't removed yet with a seeding ratio like 1.21 or 1.34 despite the desired stop seeding ratio of 1.00. Evidently it is continuing to seed when I have told it not to or misreporting. I have had this problem with v1.20 (5786) on OS X v10.5.2 Intel as well and probably earlier versions for some time. I got my MacBook 2007-12-24 so starting with Transmission v0.96 I have as I remember continuously upgraded without changing profiles. No clean reinstalls of either Transmission or OS X.

[Yada]

I've had issues in the past with per-torrent settings living their own lives but I must say I haven't seen it happening for a pretty long time now...

[Waldorf]

Yes, when a torrent finishes, its ratio limit is set to "seed forever". This is the desired behavior in most cases.

[yerfspd]

Well maybe it's desirable to seed forever for most people but that's not what I set so it shouldn't do it that way. I'll set something to seed forever after I've had a chance to check it out. If it's good quality stuff then I might seed forever but until then I want it to do what I set it to do.

[livings124]

When a torrent reaches the ratio, it stops and the ratio setting changes to seed forever. If it didn't change you wouldn't be able to start it again.

[yerfspd]

Thanks livings124. I suppose the problem with my "overseeding" is the necessity for me to remove the fully seeded torrent from the list before executing another resume all command.

[michaeltyson]

Hi! This problem is driving me bananas.

I'm in Australia, where our ISP's are anything but progressive. My ISP charges for uploads, so obviously it's critical for me that my Bittorrent client does the 'right thing' when it comes to seeding.

I set a limit of 1.05 on seeding, but this very rarely seems to actually be enforced. For about 50% of my torrents, I'll pull up Transmission only to see a seed ratio of 5 or more. This is pretty unacceptable, as it tears through my quota.

I think there needs to be a way to set this as a hard limit. Having it suddenly switch to unlimited seeding really isn't desired behaviour at all, and it's causing me some pretty annoying problems when I get towards the end of the monthly cycle and find myself shaped.

Thanks,

Mike

[BlaatMekker]

I'm experiencing the same bug, and some other bug as well. I'm using v1.40 right now. I have less data verified than I downloaded when it finished.

[chitown]

I know they say auto "seed forever" is intentional but it just doesn't seem right. I have my seed ratio set to 3 and the max seeding queues set to 3. The problem comes when the transfer completes and the seed forever turns on, the other torrents in the list are never seeded. For instance, if I have several torrents in queue and max queues are set to 3. Then the first 3 torrents get seeded a ridiculous number of times (eg 100+)... and the forth torrent is still at a ratio... 1.2

Yes, I could remove them from the list but then it makes it more difficult to generously re-seed the torrent if I see it needs it.

So, please, please, please, allow us to set a max seed ratio which actually remembers the settings.

[essiw]

I'm experiencing the same bug, and some other bug as well. I'm using v1.40 right now. I have less data verified than I downloaded when it finished.

I think everyone has that, and I don't think it is a bug, I don't know how it happens though, but as long as it is less then 1% it shouldn't matter that much

[livings124]

It is only set to "seed forever" once the ratio is reached and it's stopped. In other words, it's set to seed forever, but it's paused anyway.

This is only because, if you did choose to res-start seeding, you couldn't if the seed ratio was set and already reached. This is an intentional feature.

[mitah]

I'm not usually one to revive old threads, but this stupid "intended/desired behavior" brought me a nasty surprise over the weekend... I went away over the weekend, let my Mac Mini with Transmission running to continue downloading a torrent for a few more hours... it seems there were fluctuations in the power grid, and the Mini restarted on it's own. So far not really good, but now a problem. Problem was, Transmission had already hit the ratio for an unfinished torrent, so after starting up again it was set to seed forever.

I come home to find the torrent at a ratio of over 10 with an upload of about 60 GB... Living not in one of the bigger cities here, you have the choice between only two ISPs, both who cap the speed after reaching a certain (normally high enough) quota. This little weekend stunt cost me about one week of a normally functioning internet.

Now this was somewhat a chain of undesirable events, but I personally need someone to blame, and Transmission seems to be the culprit here.

How on earth is it possible that a program resets a user defined setting a) AT ALL and b) WITHOUT WARNING. This some of the most user-unfriendly behavior an application can show. And it seems this is one of these things where you just need to bang your head against the wall, because it's word of god that THAT'S THE WAY IT MUST BE. It's like the when Steve Jobs decides "there is no problem with the iPhone". Just saying so doesn't make it right. Transmission prides itself on functionality and no-clutter settings and interface. And i like it for that... but this behavior is just like, to take on another Apple comparison, like the new iPod shuffle. I an attempt to over-simplify a rather simple product, you just make it too simple to use it in specific ways. (try changing a playlist or rewinding a song on an iPod shuffle with only one button).

THe solution to this "problem" could be so simple as to check whether A) the user has pressed the pause button to stop a torrent, or B) if Transmission just went to sleep with the Mac or was shut down. In the case of A, it is only logically that the torrent needs to be set to seed forever, and after pressing the resume button Transmission should pop up a dialogue saying "ratio already reached, setting to seed forever". Done. But in the case of B), it is in no way desired behavior that the program on it's own just sets seeding forever, it should just finish downloading with the user-set ratio and pause the upload after reaching 100 % download.

This all can be differentiated just by a single user interaction, the pressing of a button, which btw. is the only time a program should change a user-setting (unless the user defined a specific rule to that effect or has set a checkbox in the preferences somewhere.


--
I needed to vent my frustration somewhere, and where's a better place for that than an internet message board. Sorry if my wording or tone offended someone.