Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Transmission 1.40 is out. Check the first page for the changelog and the updated download link.
Offline
Hi There,
haven't been here for a while. I just installed 1.40 after uninstalling 1.33 and deleting all former settings. I also changed the settings to my pleasing. That is when I ran into some trouble. It seemed, I had to change the SSH profile environment settings to:
export TRANSMISSION_HOME=/mnt/HD_a2/.transmission-daemon
If I didn't do that it would save the settings.json to /mnt/HD_a2/.transmission instead of /mnt/HD_a2/.transmission-daemon
you guys experienced this too?
greetz and great thanx to KyleK for this build
PS: gonna check Automatic as well.... see what it can do
Offline
Thanks man!
For some odd reason when I am trying to start torrents, it gives me Permission Denied as errorcode.. ..it doesnt download the files.
What have I done wrong?
P.S
I found what was wrong... ..I needed to have a folder for it to download the files... ..I hadnt set one correctly, problem solved!
Thanks, InfernoX.
Last edited by InfernoX (2008-11-11 07:50:52)
Offline
@egg_nostic: The default config path for Transmission is set in start/transmission.sh, so if you use that script it should pick the correct folder. Maybe you restored the old start script after updating?
Offline
@Kylek,
Now that you mention it. I did a number of re-installs. At some point I renamed the transmission.sh and reinstalled transmission again and changed the profile file. This probably made me think that the profile setting actually made it work. Seems that with the install of Transmission, the transmission.sh in /ffp/start is not (always) overwritten?
greetz
Offline
I just installed 1.4 over the top of 1.34 using "funpkg -u" and it works perfectly.
They even fixed the annoying bug where I had to upload a new torrent twice every time. Thanks Kyle.
Offline
@Muppet No problem
@egg_nostic
The start/transmission.sh is always overwritten when you install a new version of Transmission. But I was just thinking: With earlier versions of Transmission, I asked the user to place the "export TRANSMISSION_HOME" line in either the fun_plug script (for telnet users) or their profile. And back then Transmission used ".transmission" instead of ".transmission-daemon".
Maybe that line is still present on your NAS? (You can check by typing "export", although you've probably overwritten it earlier. Maybe a restart will reveal?)
I'm at work now and can't test that theory, but I'm assuming Transmission prefers the environment variable over the command-line parameter.
Offline
My root has both the ".transmission-daemon" and the ".transmission" folder. Is the latter something that was left by a version prior to 1.40? Can I remove it?
Offline
@vedeja: if you type 'top' you should see several transmission-daemon processes, and it should also show the path to the configuration file (by default /mnt/HD_a2/.transmission-daemon).
If your root is /home/root (which is on the flash), then yes, you can delete both those folders. Make sure to double-check. Looking at the date of the files inside those directories is always a good idea
Offline
My 'top' returns "/ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon" so it doesn't make sense to delete that, right? I erased the other one though.
Offline
Vielen Dank!
My friends presented me DNS 313 just a week ago so I'm just a newbie.
Is it possible that transmission makes some HD activity when seeded torrents aren't really active (UL stays in 0)? Maybe some log or files check... It seems like NAS (firmvare 1.02b04) doesn't use power managent settings and drive never turns off.
Offline
KyleK wrote:
But I was just thinking: With earlier versions of Transmission, I asked the user to place the "export TRANSMISSION_HOME" line in either the fun_plug script (for telnet users) or their profile. And back then Transmission used ".transmission" instead of ".transmission-daemon". Maybe that line is still present on your NAS?
Yes it was in my profile and I had to change it to ".transmission-daemon".
Offline
You can remove it from your profile entirely. It is only needed by transmission-daemon on startup, and that's provided in the start/transmission.sh.
(Earlier versions required the config path to be known globally, so transmission-remote would know where to look for the server. This has changed and the remote app doesn't need that info anymore)
Offline
I successfully managed the upgrade of v1.4 (with funpkg -u).
However, all my running torrents have diseapeared from the web interface....
Files were present in folders : /.transmission-daemon/resume and /transmission-daemon/torrents.
So I had to "upload" all the torrents from the web interface to get them back in the web interface list..
Did I miss something ??
greg
Offline
The update never ever touches Transmission's config folder.
Maybe you use a different config path than the default? Type "top" to see what path Transmission uses. The default is /mnt/HD_a2/.transmission-daemon.
Offline
Hi All... I'm sure this question has been asked somewhere... Possibly in a more appropiate location too, but does Transmission use DHT? Do they intend to implement it? Appriciate any opinions or knowledge shared!!!
Thanks!!
Offline
Nope, Transmission doesn't support DHT. And no, this is actually not the best place to ask this
You're going to get a better answer at the official Transmission site www.transmissionbt.com
Offline
Thanks Kyle... Great your doing great work on here. Thanks for all the help!
Offline
Quick question to someone who is using v1.4 please:
Does 1.4 it allow for time-based bandwidth scheduling through the web interface?
I'm in Australia and my ISP has peak and off-peak usage, i'm using the older version with a script that limits the bandwidth during peak times.
Offline
Bummer. Thanks for the reply i'll stick with 1.22 for now.
Offline
The new version still uses transmission-remote, and you can set the speeds via the web interface (just not by time scheduling) so it might just work if you give it a try.
Offline
Kylek.. Thanks for supporting transmission on the DNS-323 along with all our questions.
Reading through this thread I've been able to get around previous "Permission Denied" problems by deleting the .transmission-daemon folder:
rm .transmission-daemon -R
and then running the transmission start script again:
cd mnt/HD_a2/ffp/start
./transmission.sh start
I went to the web interface, change the download directory, port, and uploaded a torrent file.. and then no more "Permission Denied" problems!! Yay!
Now to figure out if anything can be done to speed up downloads (to over 30kBps).. maybe the dns is just too slow to get the 100kBps+ I can get on other machines.. (kBytes.. not kbits).
but seriously.. Thanks kyle!! You're awesome
Offline
I've had downloads with 600kB/s and more, so it's definitely possible. There should be some posts in this thread already where I mention stuff you can try.
Be advised though: Most public torrents, especially current stuff, is dog-slow with almost any client. That's just how the system works.
Also, the current version 1.40 doesn't do a good job at displaying transfer speeds. It will jump very often between low values and high values, so it might not always be a good indicator for the real speed.
Offline
yeah.. I'm noticing it bounce around more now.. even above 100kBps.. so I think it's working well
It's really nice to offload this mundane task to the dns-323.. I'm very happy having this appliance to do this work for me.. Great job with the port Kylek.. and really.. thanks
Offline