NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)
This is a newly compiled version for the Duo straight from source. It has been configured with "--disable-nls --enable-lightweight --enable-utp" and the default web interface port of 9091.
If it doesn't work after installation, try rebooting.
Not sure if it can be install over the top of super-poussin's version, but if you are planning on uninstalling super-poussin's version then remember to save the torrent files somewhere else first.
To quote myself:
Thanks to super-poussin for the original Transmission add-ons.
Enjoy!
Transmission_2.73.bin - http://www.mediafire.com/?ajpyyc7ujv54o37 no-utp
Transmission_2.75.bin - http://www.mediafire.com/?gbmbhu3hrabf9fe
Transmission_2.76.bin - http://www.mediafire.com/?389i53w9w9rtosm
Transmission_2.77.bin - http://www.mediafire.com/?pm420vuajaim9bz
Transmission_2.80.bin* - http://www.mediafire.com/?5s7dag8ko72doj1
Transmission_2.81.bin* - http://www.mediafire.com/?x4pvvidrgb36df2
Transmission_2.82.bin* - http://www.mediafire.com/?rbctsdae000zoav
Transmission_2.83.bin* - http://www.mediafire.com/?31iul25i0t12qda
Transmission_2.84.bin* - http://www.mediafire.com/?rh5fge4mc8ahzw4
*if the "Upload" button doesn't work or the "Destination folder" field is blank, reload the webpage.
If it doesn't work after installation, try rebooting.
Not sure if it can be install over the top of super-poussin's version, but if you are planning on uninstalling super-poussin's version then remember to save the torrent files somewhere else first.
To quote myself:
tarobun wrote: It looks like upgrading from Transmission 2.42 to this Transmission add-on is a no-no. Sounds like there are conflicting configuration that screws up both installs. :( (eg. /c/addons-config)
It seems the best approach is to fully uninstall the old, delete the config directory, and then install this add-on. Once you're on this add-on, updating is straightforward and can be done over the existing version.
Just a fyi - the default download dir is /var/local/Downloads and there is no username and password with this add-on. If you are prompted for them then the old version was not fully uninstalled.
Thanks to super-poussin for the original Transmission add-ons.
Enjoy!
Transmission_2.73.bin - http://www.mediafire.com/?ajpyyc7ujv54o37 no-utp
Transmission_2.75.bin - http://www.mediafire.com/?gbmbhu3hrabf9fe
Transmission_2.76.bin - http://www.mediafire.com/?389i53w9w9rtosm
Transmission_2.77.bin - http://www.mediafire.com/?pm420vuajaim9bz
Transmission_2.80.bin* - http://www.mediafire.com/?5s7dag8ko72doj1
Transmission_2.81.bin* - http://www.mediafire.com/?x4pvvidrgb36df2
Transmission_2.82.bin* - http://www.mediafire.com/?rbctsdae000zoav
Transmission_2.83.bin* - http://www.mediafire.com/?31iul25i0t12qda
Transmission_2.84.bin* - http://www.mediafire.com/?rh5fge4mc8ahzw4
*if the "Upload" button doesn't work or the "Destination folder" field is blank, reload the webpage.
159 Replies
Replies have been turned off for this discussion
- 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?
- 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) - 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'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? - 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. 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.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.- Thanks for your reply.
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.
The issue is that the folder with the new version differs from my old version.
With the new transmission the folders 'torrents' and 'resume' can be found in the root folder (\\192.168.1.105\addons-config\Transmission)
where my old torrent files can be found in the 'torrents' and 'resume' folders which are placed in the transmission-daemon folder (\\192.168.1.105\addons-config\Transmission\transmission-daemon)
I cannot copy my old files to the new folder and I don't know what I have to change to reconfigure tranmission so my old torrents can be shared again.
Is this clear and could you help me out? spacecrap wrote: Hi there,
I just upgraded to Transmission 2.81 and found out that I could enter the transmission web interface, but:
- all the downloads are gone from the overview (I probably have to add this manually?);
- New downloads won't start downloaden.
I have an open port, but the downloads just won't start, what can I do to fix this?
edit; strange.. it seems that the RPC port was still on 8181 in stead of 9091.. i changed this in the .json and one of the downloads works now... the other ones don't yet....
Hmmm... upgrading from 2.42(?) is a bit tricky as the settings.json file is retained and don't default to the 2.8x settings.
Maybe try renaming the settings.json file and restarting the addon so a fresh settings.json is created which you can then edit manually.- Updated to version 2.82 - dedicated to Russell Coight
Changes:
All Platforms- Fix webseed crash
- Fix crash when adding UDP trackers whose host's canonical name couldn't be found
- Fix crash when sending handshakes to some peers immediately after adding a magnet link
- Fix crash when parsing incoming encrypted handshakes when the user is removing the related torrent
- Add safeguard to prevent zombie processes after running a script when a torrent finishes downloading
- Fix "bad file descriptor" error
- Queued torrents no longer show up as paused after exiting & restarting
- Don't misidentify Tixati as BitTornado?
Web Client- Fix syntax error in index.html's meta name="viewport"
- Fix file uploading issue in Internet Explorer 11
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
