Transmission

Similar or same problem with 2.11. I hadn't upgraded my Unslung for a long time and found this problem. No news?
Edit: I read through the long but informative bug tracking thread...is the consensus still that it's a packaging issue? Anyway I'm willing to go back to 1.76 but I don't know how, can ...

Jordan wrote:Does the problem persist in 1.50b3?

Finally tried 1.50, and the problem is fixed. Working quite well on the little slug @ 4-5 watts.

Don't know...I'd like to try but the latest NSLU2 transmission version is 1.42. This may be the incentive I need to figure out how to do cross-compiles for it on an xubuntu lappy.

1.42 on an NSLU2 Unsling
No dl/ul limits

Successfully, tho slowly, downloading a large (40+ GB) torrent. However other torrents have no activity. In particular 3 recently added torrents have not downloaded a byte and on the transmission web interface show 0 peers or seeds, but right now when I ...

A simplified version that is entirely within awk. So your crontab line should be something like

0,30 * * * * /bin/awk -f /scripts/tr_check_ratio.awk

Also this doesn't have the exceptions feature, which would be easy to add.

Yeah, would be nice if this were part of transmission itself.

#!/bin ...

T 1.42 on an NSLU2 Unslung.

Problem with keying on T's Ratio is that T uses Ratio=Uploaded/Downloaded, which doesn't work well for torrents that were added to T already 100% downloaded. Ratio is reported as Inf and the script stops the torrent.

So below is the previous bash script and awk program ...

1.42 on an NSLU2 Unslung.

Ratio is calculated as Uploaded/Downloaded. Seems easy enough. The problem is when adding to transmission an already-downloaded torrent (from, say, another client or another computer). Then T says Downloaded is zero and reports Inf in the Ratio. More importantly to me, the ...