DSM-G600, DNS-3xx and NSA-220 Hack Forum

Thanx again, I forgot to make deamon auto-startup. And sorry to trouble with such basic things.

Is anyone else having problems downloading the latest transmission 1.51. I cannot get to Kylek's site.

-sc

The files are up again. Sorry for the downtime.

First I cant answer your question but.. on every private tracker I have ever used, uploads are aggregated across all torrents, not individually. So seeding every torrent to 1:1 is pointless because some will never reach that ratio if you join them late, and because you stop the torrents that do require seeds once you reach 1:1 on them, you never reach 1:1 overall. My advice is to consider not being selfish - it is very annoying to other users when seeders drop off just because they happened to share the bare minimum.

The current version doesn't support ratio control, but the next one will.

KyleK thanks. You have one new friend on your list !

Thanks KyleK for continuously keeping this up to date.

If downloads are slow you may also want to check to see if you are downloading to the same folder your built-in Upnp server is set to discover files. I found that the auto-update feature of the Upnp will slow transmission down dramatically since it starts to re-index the database as soon as you start to download a new torrent.

Just something to keep in mind.

breasthead wrote:

I try and access web interface and it just sits there for hours and does nothing. I then ssh into dlink and try "transmission-remote -l" to check torrent status and that takes a long time to appear (sometimes nothing for 5 min and I ctrl+c to cancel). I only have one torrent in the list so its not like it needs to get info for lots of torrents. The only thing I can do is stop transmission (/ffp/start/transmission.sh stop) and instantly the web interface comes up as "not available", then restart transmission (/ffp/start/transmission.sh start) and both "transmission-remote -l" and the web GUI come up instantly. After a while (not sure how long ...days maybe) all is back to being slow and need to restart transmission.

One thing to check is how much of the system resources transmission is using.  As KyleK mentions, 1.50 had CPU problems.  I've noticed sometimes 1.51 uses a fair amount of CPU and memory as well, but that was with a few high-activity torrents running, so I'm not sure it's a bug.

You can use the 'top' command on the DNS-323 to check CPU and memory usage.  It is similar to the Processes tab in Windows Task Manager.

Another thing to check you should check is that you have your upload limit capped appropriately.  If you notice the response time mainly when accessing the DNS over the Internet, I'd say check this first.  I forget what the exact recommended setting is, but I'd say 80% of your available upload bandwidth is safe unless you are doing other upload-intensive activities like streaming your music remotely.  You can set the upload limit with transmission-remote using the -u switch.

The WGET for the curl libraries has been failing for a few days when I try to access them at KyleK is a geek (running "wget http://kylek.is-a-geek.org:31337/files/ … .tgz" generates a Connection Refused error.) As a Linux noob, I can't figure out where else to get this library in order to try and run Transmission on a DNS-321. If Kylek is around, is there an issue with the server? Alternatively, could anyone post a link to an alternate download location for the right version of Curl 7.18.1 that works with the DNS-323/321?

lamski wrote:

I have some questions for you guys: I'm still using the 1.05 firmware version for my DNS-323. I'm thinking of upgrading to 1.06 but I'm wondering if there are any drawbacks.
If I upgrade to 1.06, do I need to reinstall ffp? I simply use the JBOD configuration for 2x 1TB disks and I have around a few hundred GBs of data (mostly downloaded media). Is it safe to simply install firmware 1.06? I read in the release notes that disks will now sleep "properly" - will this affect transmission operation?

Any input on this will be greatly appreciated.

A firmware update should not impact the functionality of funplug in any way. You won't have to reinstall ffp after upgrading.
The info in the release notes about disks sleeping properly doesn't affect Transmission in any way (the disk won't be spinning down anyway if Transmission is running - it has to read and/or write data from it).


But, in any case it would be wise to backup critical data before the firmware update.

breasthead wrote:

Is it just for me, who has 1.50 up and running, as simple as:

funpkg -r Transmission-1.50.tgz
funpkg -i Transmission-1.51.tgz

And thats it?

Don't forget to stop the transmission-daemon processes.  You need to add a couple of steps:

/ffp/start/transmission.sh stop
ps -A | grep transmission  (to check that the transmission-daemon processes have ended)
funpkg -r Transmission-1.50.tgz
funpkg -i Transmission-1.51.tgz
/ffp/start/transmission.sh start

axelsvag wrote:

I have got a newbee question. I have read a lot about the problem with the message "no such file" which seems to be connected to wrong permission or wrong download folder. Before I understood the problem I somewhat screwed up the "settings.json" file and did not understand how to change permission of the download folder. So please can someone give some advice firstly how to edit the "settings.json" file in the right way and change permission to the download folder. It is probably some more settings that should the altered.

Dont' change the settings.json by hand. Use the tools transmission-daemon and transmission-remote for that.

If you want a completely fresh start, do this:

$ /ffp/start/transmission.sh stop
$ rm -r /mnt/HD_a2/.transmission-daemon   (this deletes all your current settings as well as progress info about currently downloading torrents!)

$ transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u <login> -v <password> -a "*.*.*.* -w /mnt/HD_a2/Downloads
[Press Ctrl-C after a maybe 20 seconds].
$ chown -R nobody /mnt/HD_a2/.transmission-daemon /mnt/HD_a2/Downloads

From here on out, only use /ffp/start/transmission.sh to start and stop the application.

Last edited by KyleK (2009-03-24 15:29:26)