Transmission

Giving this a whirl now. Thanks.

Hi all,

I've been using Transmission for a while now on my home server which I recently upgraded. The issue I've always had with Transmission is one of permissions. When a file is finished downloading and moved to my Complete folder, its owner is set to debian-transmission (as listed in init.d ...

I'm very new to Linux so inotify is a new one to me. I'll do some reading on it. Do I need to do anything specific to get Transmission set up to use it?

According to a helpful poster in the Support subforum the interval at which Transmission checks the watch directory is hardcoded for 10 seconds. This seems a bit excessive and prevents the disk on which the directory resides from ever sleeping as it's being accessed constantly.

An option in the ...

Title says it all. I've searched and I've searched and haven't found a way to do this. Right now it appears watch-dir has Transmission checking that directory every few seconds. I'd like to set it to once every 15 minutes, maybe even an hour. Is this doable?

Seeing the same thing here. I have a NAS running 1.93 and an actual desktop running 2.00. I set the same two torrents on both and 1.93 was much faster. Different machines I know, but honestly the desktop should be faster as it has infinitely more resources than that little NAS.

Now I really can't wait for 1.80, heh.

Looks like I spoke too soon. Transmission was running sluggish (slow to update to Transmission Remote) so I ran a top and it was pegged at 100% CPU usage. Stopped Transmission and restarted it and all is well again.

For what it's worth, I turned off DHT and PEX and set encryption to 0 and I haven't had to reboot my DNS-321 in two days. I didn't seem to help at first in terms of CPU utilisation, but it certainly does now.

I run 1.76 on a dinky NAS processor so I turned off PEX and DHT and encryption and that seemed to help a little on the CPU utilization. Still a lot higher than I would have expected it to be judging by posts I've seen on this forum and another.

Slightly off-topic, but somewhat relevant...

I've noticed similar patterns on my DNS-321 NAS. When Transmission starts up with two active torrents it typically eats 15-30% of the CPU (it fluctuates wildly, but that's not the problem). After being up for about ~12 hours that usage goes up to over 50 ...

Look :
There's no limit, that server is running with default values. The big difference is the torrent, it is being served by a private tracker.

http://img121.imageshack.us/img121/9075/transmissioni.jpg

This same torrent hits 600kB/sec in uTorrent. It has yet to break 100kB/sec in Transmission ...

I understand all of that, but I still don't get the 15 peer limitation. I can load this exact same torrent with 1100 peers in the swarm into uTorrent and easily reach 300kB/sec from over 100 peers, whereas I'm seeing at the very most 50kB/sec in Transmission. That's usually more like 10kB. My DIR ...

Seriously? 15 connections for downloading with no way to change that? I'm currently downloading at 10kB/sec on a torrent with 1100 peers. If there's no way around that limit Transmission seems kind of... well, pointless.

Can anyone verify this?

This is exactly the issue I'm running into. I even set peers per torrent up to 200. In Transmission Remote (when it actually connects to the daemon) I have torrents showing 13925(15) Leechers. So it's not connecting to many peers.

I'm sure it's something I'm doing wrong, because I've seen posters ...