Transmission

CokeWins wrote:I'm also trying out the new on-complete-script, and while my script does seem to get run, it seems to freeze/block transmission until it finishes, and it starts when transmission still shows 99% complete, so my seeding detection logic doesn't work.

So I have 2 questions:
1) When does the script get fired? After 100% complete? Just at 100% complete?
2) Does the script freeze/block transmission while it runs? Can I run it asynchronously at completion?

If it helps, I compiled it myself and I'm running it on my DNS-321

Thanks.

1) The script gets called after the torrent's state changes. It sets a bunch of environmental variables right now to communicate with the script. Look at the example script.
2) The script call currently blocks. That's easy enough to get around if you need to.

Longinus00 wrote:

CokeWins wrote:I'm also trying out the new on-complete-script, and while my script does seem to get run, it seems to freeze/block transmission until it finishes, and it starts when transmission still shows 99% complete, so my seeding detection logic doesn't work.

So I have 2 questions:
1) When does the script get fired? After 100% complete? Just at 100% complete?
2) Does the script freeze/block transmission while it runs? Can I run it asynchronously at completion?

If it helps, I compiled it myself and I'm running it on my DNS-321

Thanks.

1) The script gets called after the torrent's state changes. It sets a bunch of environmental variables right now to communicate with the script. Look at the example script.
2) The script call currently blocks. That's easy enough to get around if you need to.

Thanks for the advice. I updated my script to take advantage of the environment variables, and added a & to prevent it from blocking transmission. Now I can have my script automatically add the next torrent when the previous completes. My NAS seems to handle multiple seeds just fine, but multiple downloads make it croak.

Thanks to the developers for all the hard work!

Aha! Found my issue with the script... or more precisely, the logfile. It wasn't writable by the user running transmission. Once I fixed that, everything worked perfectly. I modified my script to write out the environment variables and found these:

'TR_TORRENT_NAME'
'TR_TORRENT_DIR'
'TR_TORRENT_ID'
'TR_APP_VERSION'
'TR_TORRENT_HASH'
'TR_TIME_LOCALTIME'

Enjoy!

Well im happy to say that this release seems to be VERY stable for me.

No errors/crashes with the changeover with speed limits turning on/off.

I do notice that there seems to be a lot less seeds/peers compared to the same torrent loaded in utorrent but its not really affecting the speeds to the point that it makes it too slow to download.

Keep up the good work guys.

just bumped up to Transmission 2.00b2 (10722) and it looks fine so far running a couple torrent tests.

one difference i noticed from 2.00b1 is the faster file verification time -- that helped a lot as it used to be so painfully slow.

I've been running 2.00b2 (10722) on my macbook (running 10.5.8) for the last 30 hours without any problems.

2.00b2 released?

no problems yet on Power PC 1,6 GHz with MacOS 10.5.8 installed.

thanks for the great soft.

Got 2.00b2 running om my iMac (2.0Ghz, 4GB RAM) with a 25mbps high speed broadband. When the downloads start getting almost to the max of my internet connection, the application starts to have a hard time responding to clicks on buttons (you'll see that spinning ball coming up when you click). But when it cools down and downloads are completed, I see a lot of 'failed its checksum test' messages in the log. Downloaded stuff is without corrupt data though. But that's as much as it gets, the rest is nicely done! Great work as always.

Ive been running 2.00b2. It's working fine for me. Connecting to peers seems to have improved. I'm getting much more consistent connections to peers in terms or uploading and downloading.

Is there a way to change the symbols for Uploading/ Downloading either into something else or have them colorized?

well i have just had to roll back from 2.00b2 to 2.00b1.

b1 had no issues and was super fast with connections, finding peers and no unexpected crashes with switching from limited speed to non limited.

But b2 seemed to be super slow, always seemed to drop the connection to 0.0k, was having issues with connecting to more than 3 peers at any one time even though now it hits the max peers of say 250 peers per torrent. (which is really no good if only 3 can transfer the data)

hopefully b3 will fix any changes.

Tried both 2.00b2 and 2.00b1 on my NAS with Marvel Kirkwood 88F6281 ARM cpu.
The cpu usage of 2.00bX is much higher then 1.93. The second issue is the speed.
I have ADSL line, and the speed limits for transmission are 400/60 KB/c. The line does not hold 60KB/c upload speed when transmission is downloading 400KB/c. The lot of SYN/ACK packets cause upload speed to drop when downloading with 1.93. This is normal.

With 2.00bX the behavior is different. The upload speed does not drop, but the download speed does not go to the maximum. If I lower the upload speed limit in transmission - the download speed goes higher. Was there some change in TOS fields that are handled by the shaper in my router?

Suddenly I noticed a bug. Sometimes when a download is completed it is paused immediately. Seeding ratio is set on 1.0, so it has to remain active. No messages in the log can be found. Some will not be paused and remain active after completion.