Transmission add-on thread before MAY 2K10

[btaroli]

Would someone be so kind as to explain how to access/edit the config file for Transmission? I cannot see it in either my media or backup share when browsing the NAS.

You should notice two new "shares" in the share list in Frontview. If you enable CIFS on the "-config" one, or use the \\(nas)\c share as "admin" and navigate to "addons-config" folder, then you should find the "Transmission\transmission-daemon" folders, in which the configuration file exists.

I have installed 1.60beta 1.

I would recommend 1.60 final, since it was uploaded just a day ago

[athomson]

slewis1972 this is the info you wanted.

After the removal of Transmission lite beta and the re-boot I cleared the files from addons-config/transmission and addons-scripts/transmission. I then Installed Transmission 1.59 (the non-beta, full edition). I stopped the addon and amended the scripts and config to say keep seeding until ratio = 4.0 and for 480 hours. I then started transmission and added my .torrent files. All was well again from then.

Andy

[Energo]

I've found that if the torrent is inside directory (not depending from how many files inside) and when you delete this torrent in web interface... directory stays. It is empty - all files are deleted but the directory for some reason stays always untouched.

[Binks]

I just wanted to post and say that the Transmission 1.60 add-on is incredibly faster than the 1.60 Beta version. I was waiting what felt like hours for the web interface and my Transmission Remote software to link up with the NAS and display information on the torrent.

With the release version, Transmission Remote is about as fast as the UI for uTorrent is when it's running on my PC.

I don't know if you tweaked it, super-poussin, or if something else caused the user interface speed boost; but I'd just like to say thanks and report that it's working great!

[super-poussin]

I just wanted to post and say that the Transmission 1.60 add-on is incredibly faster than the 1.60 Beta version. I was waiting what felt like hours for the web interface and my Transmission Remote software to link up with the NAS and display information on the torrent.

With the release version, Transmission Remote is about as fast as the UI for uTorrent is when it's running on my PC.

I don't know if you tweaked it, super-poussin, or if something else caused the user interface speed boost; but I'd just like to say thanks and report that it's working great!

Thnak you

[majello]

Hello everybody!

For those of you that have problem with permissions, i suggest modifying the start script of transmission to set the proper permissions.
To do that, edit the file "/etc/frontview/addons/bin/TRANSMISSION/start.sh" using the ssh access and modify the line startting with "start-stop-daemon" to include the following:

"-g users" -> will set the daemons group to the group "users". of course you need to have that group on your nas.
"-k 0002" -> sets the so called umask and will allow user and group read/write-access, and read access to everybody
"--chuid nobody:users"

so my start.sh says:
start-stop-daemon --chuid nobody:users -g users -k 0002 --start --pidfile /var/run/transmission-daemon.pid --make-pidfile \
--exec /usr/local/bin/transmission-daemon --background --nicelevel 5 -- -g /c/addons-config/Transmission/transmission-daemon

Next on the list: get the web interface to actually report errors it gets from the daemon so i can tell if the interface is slow or the url is nonsense. and then get some sort of reporting for the daemon working. it is kind of annoying that it leaves no trace in the logfiles.

cheers

majello

[LCL]

I have some trouble with transmission on my duo..
It works good at the beginning, but then after a while its starts to activate torrents of some sort, in my case iam seeding 4 torrents, after a while its sending to the tracker that iam seeding 20 torrents but only 4 are listed on the remote gui..

at this point transmission gets really slow as it would if it had alot of torrents active. long loading time for remote. frontview gets killed only a reboot will bring it back, until transmission starts to activate alot of torrents, then it gets killed again.

this happend with 1.594 light and 1.60 light

[Lover]

After I installed Transmission 1.60 I see in remote that its Transmission 1.60b1. Could you check that please? I have downloaded the last light version in Community Add-ons.

Thanks.

[super-poussin]

I download the code again and will compile it again to see

[super-poussin]

After I installed Transmission 1.60 I see in remote that its Transmission 1.60b1. Could you check that please? I have downloaded the last light version in Community Add-ons.

Thanks.

download it again

[Lover]

After I installed Transmission 1.60 I see in remote that its Transmission 1.60b1. Could you check that please? I have downloaded the last light version in Community Add-ons.

Thanks.

download it again

super-poussin,

Great. It works now.

Thanks.

[btaroli]

so does this mean that what was posted as 1.60 was really still 1.60b1?

[zgz]

I used Transmission a while back but my router kept crashing so I removed it and went back to the default BitTorrent client. I just bought a new router and would like try transmission again; it's moved on quite a bit! So if it is not too much trouble I have 2 newbie questions:
- The latest version has no watchdog - is the watchdog function (auto add torrent files from a specified dir) removed? That was very useful.
- I do not see a 'webroot' share on my readynas, where is the 'transmission-daemon' folder that is mentioned in the first post? (I do see this folder in the addson-config folder, is it the same?)

[RWright]

After I installed Transmission 1.60 I see in remote that its Transmission 1.60b1. Could you check that please? I have downloaded the last light version in Community Add-ons.

Thanks.

I cannot find anything in Transmission remote that reports the version of the client. Where do I find this ?

Thanks ...

[super-poussin]

so does this mean that what was posted as 1.60 was really still 1.60b1?

sounds like when they announce the 1.60 they did not update the code