Transmission

Hmm... I tried another torrent client (deluge 1.2-rc4) and observed similar thing - slow leakage of 'up' bandwidth, though to a lesser degree. Probably it's a protocol thing after all. My concern is that all the connections I'm seeing on the 'idle' transmission client are UDP ones coming to the list...

Hi, I'm experiencing a weird problem running TBT 1.76 compiled from source on Ubuntu 8.04.2. After downloading a bunch of files, I removed all torrents, as well as downloaded data, from the WebUI. Now every time I restart the daemon, I do see pristine blank interface with no torrents at all. The pro...

Well, yet another question is whether those options would be available in the WebUI / daemon version of the transmission? If so, what the name of those options will be or at least how to generate a default config file with default settings in (which can be used as a basis for further tunings)...

The same problem here. The daemon setting USED to work (I believe in 1.72), but once 'umask' setting in the settings file got introduced, the daemon setting is seemed to be ignored. Startup string for daemon with UMASK set: start-stop-daemon --chuid $USERNAME --start --pidfile $PIDFILE --make-pidfil...

Seems like the name of the properties have changed, which is not reflected in WIKI. See this post: http://forum.transmissionbt.com/viewtop ... 460#p37460

In fact, it works. Thanks for the tip. The WIKI is out of date then. PS: FYI, similar settings are used to set 'download' limits as well: "speed-limit-down": 400, "speed-limit-down-enabled": true, "speed-limit-up": 25, "speed-limit-up-enabled": true,

Quite a few people did (I'm among them). Unfortunately, the board is not very responsive. Still haven't figure out a way to know whether a problem report has been acknowledged or not...

Have the same problem after upgrading to SVN 8322 (either 1.6beta1 or couple of updates later). settings.json file for daemon is not longer being read. Has the default TRANSMISSION_HOME directory changed? I'm not redefining it right now in the init.d script, so it (supposedly) defaults to $HOME/.con...

I do confirm the same issue - transmission does have adverse effect on the network in the described manner. Using SVN build 7931.

Vlad

Interestingly, have exactly the same experience! The downloads are starting relatively fast, but after a while they just die down!!! Tried deluge - works as expected - no slowdown during the whole time of the download...

Hmm - compiled from the trunk the other day - the performance is way better... Will let it run for a day or two - prob. it's not as hopeless as I initially thought .

I'm running beta4 now.... Don't see any difference to compare with 1.42. Albeit, I'm running beta4 from PPE - haven't been compiling it myself. Which version do you use? Have the DHT been included in the latest beta4?

Yep - I managed to generate settings.json file once run the transmission in the GUI mode and the 'watch-dir' (or smth like that) property got generated. Albeit, for some reason the transmission-daemon doesn't pick it up (not sure if the GUI app does). Also, browsed the code a bit and it's not in the...

Hi,

I wonder where does transmission-daemon log any errors or status (if any)? So far I was unable to find any reference to the location of the log file or configuration setting for that...

Thanks,

Vlad

Yeap, I vote for this one too. The next best thing to the complete settings file I got to was to run transmission from the desktop, which generated settings.json file with much more settings that are covered on the trac. Running transmission in headless mode is very hard because quite important sett...