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

I've packaged up Transmission 2.20 beta2 for you guys to test.

Important: I've made changes to the startup script (/ffp/start/transmissions.h) and modified the path where Transmission stores its settings. This is to make it more concise with how other daemons do it.
Transmission settings will now be saved in the folder /ffp/var/transmission (previously: /mnt/HD_a2/.transmission-daemon), the logfile will be stored at /ffp/var/log/transmission-daemon.log (previously: /mnt/HD_a2/.transmission-daemon/transmission-daemon.log)
Also, Transmission is now started as a real daemon (before it always ran in foreground and was forced into a bg process by the shell).


If you want to go with these changes, make sure to copy/move your current settings folder to the new location:

$ mv /mnt/HD_a2/.transmission-daemon /ffp/var/transmission

Folder and files should also have the same user rights as before the move.


If you don't want this change, just make a copy of your current /ffp/start/transmission.sh, install the beta, and then simply copy back your script.

athlonx wrote:

@wtfok

Not sure is the same as yours, maybe you can take a look. 

http://dns323.kood.org/forum/viewtopic.php?id=6147

Thank you so much athlonx, this worked! For the record: I had to actually set my DNS servers in order to ping to a hostname instead of an IP. I set them to Google's open DNS servers, 8.8.8.8 and 8.8.4.4, just like you (and just like my PC, hehe)

rsd76 wrote:

@wtfok
You cannot ping http adresses of addresses with port number.
You can "ping tracker.istole.it" in your case. Or at least try. The server might not respond to pings.
Or you can try "telnet tracker.istole.it 80" to connect to a server + port.  (In my case press enter a couple of times and I got a response.  Otherwise try CTRL^C and 'e'.)

You can even try "wget http://tracker.istole.it:80" to check if a html page can be downloaded.

Thanks for your help. After setting the DNS servers in the NAS, I got this working.

wtfok wrote:

athlonx wrote:

@wtfok

Not sure is the same as yours, maybe you can take a look. 

http://dns323.kood.org/forum/viewtopic.php?id=6147

Thank you so much athlonx, this worked! For the record: I had to actually set my DNS servers in order to ping to a hostname instead of an IP. I set them to Google's open DNS servers, 8.8.8.8 and 8.8.4.4, just like you (and just like my PC, hehe)

No problem, I was pulling my hair when i was stuck at this stage.

This is one of the most important step. If not, the trackers will never start.

Ruebban wrote:

ANyone maybe wanna help me with my annoying problem?

When I, for example, want to alter my settings.json file, I have to stop the Transmission daemon first. When I have done so, I can just open it, else I can't. When I'm finished editing, I just start Transmission again, and the file becomes unwritable automaticly.

Maybe that'll work for you?

Ruebban wrote:

Well, its in the /downloads/ folders, where my finished torrents are, when i wanna delete them, it says i dont have permission, but do you think it can help  by stopping transmission ,if so, how do i stop it? And how do i start it again?

Edit: It didnt work with stopping transmission, i still cant delete files in my downloads folder.

Did you stop it this way?
/mnt/HD_a2/ffp/start/transmission.sh stop

Check if the service has indeed stopped with /mnt/HD_a2/ffp/start/transmission.sh status

If you still have trouble, you should indeed chmod that particular folder. Consider the security issues, though.

KyleK wrote:

I've packaged up Transmission 2.20 beta2 for you guys to test.

Important: I've made changes to the startup script (/ffp/start/transmissions.h) and modified the path where Transmission stores its settings. This is to make it more concise with how other daemons do it.
Transmission settings will now be saved in the folder /ffp/var/transmission (previously: /mnt/HD_a2/.transmission-daemon), the logfile will be stored at /ffp/var/log/transmission-daemon.log (previously: /mnt/HD_a2/.transmission-daemon/transmission-daemon.log)
Also, Transmission is now started as a real daemon (before it always ran in foreground and was forced into a bg process by the shell).


If you want to go with these changes, make sure to copy/move your current settings folder to the new location:

Code:

$ mv /mnt/HD_a2/.transmission-daemon /ffp/var/transmission

Folder and files should also have the same user rights as before the move.


If you don't want this change, just make a copy of your current /ffp/start/transmission.sh, install the beta, and then simply copy back your script.

Is there a changelog for this new beta? Does your version numbering follow those from the official transmission project?

Thanks for your work on this and automatic. It has made my life a lot easier

Hm. I wonder if that is because Transmission is running as a real daemon with the new script.
I'll investigate.

nfora wrote:

I installed the new build, and it worked alright. I did have to create /ffp/var/log/ and copy my old transmission-daemon.log file into it.

It looks like 2.20 has issues with folder watching, however, so I downgraded to 2.13. I kept the new startup script, and it seems to work fine with the old build.

I also confirm that the /ffp/vag/log/ was not created during the installation.
I created the directory manually but I now get the following error message upon starting up:

"Couldn't open "/ffp/var/log/transmission-daemon.log": Permission denied".
What permissions should I give to the /ffp/var/log/ dir and how?
Btw should I also move the transmission.log file ?

Transmission v2.20 is out! Get it from the first post.

I see this as a maintenance release, bringing performance improvements and fixes several bugs.

@nfora Watchfolder should work again with this release. There was a regression somewhere between the betas. Please test it and let me know if it works.

KyleK wrote:

Transmission v2.20 is out! Get it from the first post.

I see this as a maintenance release, bringing performance improvements and fixes several bugs.

@nfora Watchfolder should work again with this release. There was a regression somewhere between the betas. Please test it and let me know if it works.

Had to massage the startup script's paths a bit, but it's looking good, and seems to be working with watch folders. Thanks!

tanstaafl1963 wrote:

Thanks KyleK!

I just upgraded from 1.92 to 2.20 with only a minor glitch.. overwrote my settings.json file but I figured it out

A few questions:
1.  how can I determine the ' "blocklist-url": "http://www.example.com/blocklist", " is functioning? I've put in
    "blocklist-url": "http://www.bluetack.co.uk/config/level1.gz" as my url...

2. I had also swapped hard drives and have an extensive list of .torrents I've downloaded, including some RSS Feeds.  Before I start up automatic again, what do I need to do to make sure my  new installation knows I've already downloaded files in an RSS Feed?  I don't want to re-download last season's Burn Notice, or Season 6 of Lost again

Thanks for the great product!!

I'm not really sure if Transmission (the daemon anyway) can automatically update the blocklist at a given interval. (I dont use a blocklist myself).
There is, however, a transmission-remote command to update the blocklist:

$ transmission-remote --blocklist-update

This will presumably use the url you specified to download and unpack a blocklist.

To enable the blocklist, set 'blocklist-enabled' in settings.json to true.

Regarding your second question: Automatic stores a list of of torrents it has downloaded already to prevent redownloading. The file is called automatic.state and by default saved at /mnt/HD_a2/.transmission-daemon. Check if the file is there.

Last edited by KyleK (2011-02-07 23:24:01)

I believe the blocklist is updated when the daemon is started.  When you run the daemon from the command line - like shown on the first post it shows the blocklist updating. And I assume it is updated by the transmisson.sh script, so you might need to restart that script every so often.  Also since I run as my user I set up for login to the drive I don't run as "nobody" so I have to go into the script and change that or else it can't create the log file.