New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)

tarobun wrote:

spacecrap wrote: I can only change the settings.json file in the 'transmission-deamon' folder... but when I change the name and start + close down transmission nothing changes. Is there a settings.json in the /addons-config/Transmission/ folder? That's the one you should be changing. The other one is now unused. spacecrap wrote: I cannot copy my old files to the new folder and I don't know what I have to change to reconfigure transmission so my old torrents can be shared again. Why can't you copy the files to the new folder? Do you get an error? There are 2 way to get your old torrents back: 1) You'll need to move all the *.torrent files in /addons-config/Transmission/transmission-daemon/torrents to /addons-config/Transmission/torrents and change your download dir to point to the old folder. 2) Edit the /etc/frontview/addons/bin/TRANSMISSION/start.sh and change TRANSMISSION_HOME=/c/addons-config/Transmission to TRANSMISSION_HOME=/c/addons-config/Transmission/transmission-daemon (and also remember to do so each time you upgrade the addon). Option 1) is the preferable one.

There is a settings.json file in the transmission folder, but this cannot be edited. I tried that without succes.
When I want to copy files it gives the error that the disk is full or protected against copying.

The strange thing is that Transmission was not working correct, but after editting the file in the transmission-daemon folder it did work... so it almost seems that this folder still is used.

I am at work now so I cannot test your option 2, but I will do this this afternoon. I will keep you posted.

so, I'm at home now and tried to acces the settings.json file. The following sign comes up: "acces to *blabla* was denied"

I will now try the second option you advised.

i've opened the transtart.ch file and this came up:

#!/bin/sh
# *************
# transmission start by super-poussin
# *************
# Variables
#
# Path to transmission-remote
REMOTE="/usr/local/bin/transmission-remote"

# Options to be passed to transmission-remote
TRANSOPT=" localhost:8181 -n admin:password1"
# *************



#LIST=`cat /c/addons-config/Transmission/seeding.txt`
#for ID in $LIST; do
# $REMOTE $TRANSOPT --torrent $ID --start > /dev/null
#done

#LIST=`cat /c/addons-config/Transmission/downloading.txt`
#for ID in $LIST; do
# $REMOTE $TRANSOPT --torrent $ID --start > /dev/null
#done

#LIST=`cat /c/addons-config/Transmission/idle.txt`
#for ID in $LIST; do
# $REMOTE $TRANSOPT --torrent $ID --start > /dev/null
#done

what do I have to change?

Nope the file is called "start.sh", not the "transtart.sh" (that's the old one).

Change "start.sh" as follows (difference is in bold).

From:

#!/bin/bash # # This should contain necessary code to start the service export TRANSMISSION_HOME=/c/addons-config/Transmission export TRANSMISSION_WEB_HOME=/etc/frontview/addons/ui/TRANSMISSION/web ARGS="-f" [ -f /c/addons-config/Transmission/settings.json ] || ARGS="$ARGS -a 127.0.0.1,10.0.0.*,192.168.*.* -w /c/media/BitTorrent" start-stop-daemon --start --chuid nobody:nogroup --umask 0 --nicelevel 19 \ --background --quiet --make-pidfile --pidfile /var/run/TRANSMISSION.pid \ --exec /etc/frontview/addons/bin/TRANSMISSION/transmission-daemon -- $ARGS

To:

#!/bin/bash # # This should contain necessary code to start the service export TRANSMISSION_HOME=/c/addons-config/Transmission/transmission-daemon export TRANSMISSION_WEB_HOME=/etc/frontview/addons/ui/TRANSMISSION/web ARGS="-f" [ -f /c/addons-config/Transmission/settings.json ] || ARGS="$ARGS -a 127.0.0.1,10.0.0.*,192.168.*.* -w /c/media/BitTorrent" start-stop-daemon --start --chuid nobody:nogroup --umask 0 --nicelevel 19 \ --background --quiet --make-pidfile --pidfile /var/run/TRANSMISSION.pid \ --exec /etc/frontview/addons/bin/TRANSMISSION/transmission-daemon -- $ARGS

Also running the following command should make all files under /addons-config read/writable.

chown -R nobody.nogroup /c/addons-config

I cannot find any file that is called start.sh.... :(
maybe a clean install would do the trick?

And I'm starting to feel like a noob, but how do I enter a command line? I tried to find out on the www and ended up with putty icw. rootssh but it seems that the command line you noted has no effect.... (i know I'm missing something... but what)

When I alter the settings from the web interface; They apply but don't seem to alter the /addons-config/Transmission/settings.json file. Where do these get stored?

spacecrap wrote:
I cannot find any file that is called start.sh.... :( maybe a clean install would do the trick?

The file should be in /etc/frontview/addons/bin/TRANSMISSION if it's not that the new version has not installed correctly. What version does it say on the ReadyNAS FrontView addon services tab?

spacecrap wrote:
And I'm starting to feel like a noob, but how do I enter a command line? I tried to find out on the www and ended up with putty icw. rootssh but it seems that the command line you noted has no effect.... (i know I'm missing something... but what)

If the command was run successfully you should be able to open/edit any files in /addons-config/Transmission -> No more "access denied".

AlTaiR wrote:
When I alter the settings from the web interface; They apply but don't seem to alter the /addons-config/Transmission/settings.json file. Where do these get stored?

The settings.json file is only saved when the Transmission service stops (via the ReadyNAS FrontView addon services tab) or when the ReadyNAS shuts down.

I have been having a problem which, if I think about it, has only occurred since I upgraded to Transmission v2.8.1 and that is that I am unable to move anything out of the BitTorrent folder or rename anything in it or in subfolders. I am asked for my password which is then apparently rejected as the action is not carried out. If I copy the files to my MacBook, I have the same problem there with the only exception that my password is accepted.

The only way to do anything is to go into Frontview and reset the share's permissions but that needs doing every time because the next time I want to rename or move anything, it happens again.

I have been trying to figure this out for some time now but just realised that, as far as I know, it is only the BitTorrent folder that is affected. I don't see any mention of this issue in the release notes of 2.8.2 so I don't know if this is a known issue or just something which I am experiencing but I am wondering if Transmission is setting the file/folder permissions or maybe it is not doing something it should do.

Can anybody shed some light on this for me as it is driving me insane having to continuously reset permissions.

I think they changed something in Transmission 2.8x...

What is the umask value in your settings.json file? Can you try it with "umask":0 ?