Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Thanks KyleK. Works fine here
Offline
Thanks from me too - upgraded fine.
RAP
Offline
Thank you again Kylek.
DL mirror :
http://rapidshare.com/files/189304736/T … 1.42-1.tgz
http://rapidshare.com/files/198405850/T … n-1.50.tgz
http://rapidshare.com/files/198408161/u … 9.29-7.tgz
http://rapidshare.com/files/198408078/curl-7.18.1.tgz
Offline
yes, it rox.
and for those who do not yet know - http://code.google.com/p/transmisson-remote-gui/
Offline
duh
i wonder, what did you expect to happen when you typed in "vi settings.json" ?
For your whitelist problem, you need to update the following line in settings.json, to something like:
"rpc-whitelist": "127.0.0.1, 192.168.0.*",
192.168.0.*, in my case, is all PCs on my local network..
Do ipconfig on your machine to check what your IP is, and add that there, for example:
"rpc-whitelist": "127.0.0.1, 192.168.1.100",
Last edited by nickdns (2009-02-15 18:40:08)
Offline
If you're not familiar with vi, I suggest you try nano instead. It's available in fonz's repository.
I prefer it to vi because it's easier to use.
Offline
KyleK
thank you! new version works fine and faster as for me
Offline
U dont need to edit the settings.json file.
just edit the line in /ffp/start/transmission.sh - search for "su $user -c "$command" line
and add the ' -a "*.*.*.*" ' option, like me- here is my line :
su $user -c "$command -B -a "*.*.*.*" -f -g ${TRANSMISSION_HOME} 1>${TRANSMISSION_HOME}/$name.log 2>&1 &"
regards
Offline
Thanks for the quick update Kylek!
I had some trouble editing the settings.json. Starting Transmission erased any modifications. I solved it by setting the settings using the suggested command line command:
transmission-daemon -f -a 127.0.0.1,192.168.1.* -g /mnt/HD_a2/.transmission-daemon/
Don't forget the 'f', because Transmission will run in the background otherwise and you might end up running multiple instances of Transmission (as I did). This might have had something to do with the inability to write the settings.json . Running "Killall transmission-daemon" solved it.
After hitting CTRL+C I could start Transmission using the usual
/mnt/HD_a2/ffp/start/transmission.sh start
I love the new (old actually) feature to add a new torrent by providing the url the the torrent!
Offline
please help me
after start transmission ver 1.5
a see in transmission-daemon.log
Couldn't create socket: Address family not supported by protocol Blocklist "level1.bin" updated with 8 entries Blocklist "level1.bin" contains 8 entries RPC Server: Adding address to whitelist: 127.0.0.1 RPC Server: Adding address to whitelist: 192.168.1.* RPC Server: Serving RPC and Web requests on port 9091 RPC Server: Whitelist enabled Transmission 1.50 (7891) started Blocklist "level1.bin" contains 8 entries Loaded 18 torrents Port Forwarding: Opened port 51413 on 0.0.0.0 to listen for incoming peer connections
wtf
Couldn't create socket: Address family not supported by protocol
???
Offline
You can ignore that. Transmission tries to open an IPv6 connection, which isn't possible on the NAS, so this message appears.
Offline
KyleK wrote:
zxsix wrote:
as torrents complete and are saved into the /mnt/HD_a2/downloads folder, the owner on all newly created files is 'noboby'.
Is there a way I can change the default owner to 'zxsix' instead? This keeps me from being able to delete these folders via windows file explorer.
If I do a chown zxsix * -R on the nas box, then I can delete the folders via windows but have to do that each time unless I can get the default ownership set up correctly.Yes, you can change the name of the owner in the startup script (/ffp/start/transmission.sh)
Please note that once you changed the name there, you have to change the owner of all configuration files and all currently downloading files as well:Code:
/ffp/start/transmission.sh stop <change the username in the script> chown -R zxsix /mnt/HD_a2/.transmission-daemon chown -R zxsix /mnt/HD_a2/downloads /ffp/start/transmission.sh start
Can anybody tell me what i need to change in the transmission.sh to change the user name under which downloaded files are created?
Offline
Just open the script in an editor (vi, nano, ...), and it'll jump right into your face.
There's a line:
user=nobody
I think you can figure out the rest :)
Offline
KyleK wrote:
Just open the script in an editor (vi, nano, ...), and it'll jump right into your face.
There's a line:Code:
user=nobodyI think you can figure out the rest
Euhm, the line is not there. It looks like this:
transmission_stop() { echo "Stopping $name" /ffp/bin/killall $name } transmission_status() { _pids=$(pidof $name) if test -n "$_pids"; then echo "$name is running" else echo "$name not running" fi } run_rc_command "$1"
Should i just add the line you mentioned somewhere?
Offline
Hm, then your transmission.sh is not up to date. Check the latest .tgz, it's in there.
Offline
KyleK wrote:
Hm, then your transmission.sh is not up to date. Check the latest .tgz, it's in there.
Hm, i downloaded the latest version. I replaced the transmission.sh with the one within the archive and changed it. Works like a charm now, thanks for the hint
Offline
i updated yesterday and it is really a much better version. Nice work dev team!
Offline
Thanks, works great! I thought they added the ability to select files from torrents to download, or is this only in the CL and not the remote?
Offline
With about 30 torrents seeding and 1 downloading CPU is constantly at 100%.
Is it normal? It seems 1.42 was better in those terms.
Offline
romanl wrote:
With about 30 torrents seeding and 1 downloading CPU is constantly at 100%.
Is it normal? It seems 1.42 was better in those terms.
I dont seem to have that problem. But i have heard similar things with others..
Offline
I'm getting the same problem. The download speed isn't great either. Can someone post their settings.json.... just in case it's something there.
Offline
When I deleted that one downloading torrent (it originated from thepiratebay.org, yes, I know, I know) the things returned to normal.
The Pirate Bay uses two trackers - TCP and UDP, so this may be the issue.
I'll post it to Transmission's Issue tracking system.
Offline
I frequently get the web interface pop up that says i have lost connection, but if i refresh the page everything seems fine.
Any ideas?
Offline
I'm having difficulty connecting to the UI as well. When only 1 torrent is active it seems to work ok. But with 2 or more i get timeouts and sometimes it won't even connect.
Offline
Hello....
After loads of tweeking I finally got the transmission 1.50 up and going (tweaking because im not* very good at linux, so have to do a man command for everything)
I had alot of problems getting transmission to axcepting my internal ip's, but after a while i figured out what the trick was:
root@blackbox:/mnt/HD_a2/ffp/bin# /ffp/start/transmission.sh stop
root@blackbox:/mnt/HD_a2/ffp/bin# transmission-daemon -a 192.168.0.*
root@blackbox:/mnt/HD_a2/ffp/bin# transmission-daemon -w /mnt/HD_a2/incoming/
root@blackbox:/mnt/HD_a2/ffp/bin# /ffp/start/transmission.sh start
But i have a problem when i reboot the nas disk...
All my settings and torrents dissapears...
I have to enter the code (pasted) all over again for each reboot.
Also, torrents downloading/seeding dissapears from transmission, so i have to open them again to continue.
Any idea what this might be ?
Also:
I HAD speed problems with the transmission 1.32... couldn't get my dwnld or upld speed past 15/15...
With transmission 1.50 I don't have a speed problem anymore.
I now get full 3.2Mb/s both up and down.
prolly more allowed global connections....?
*typo
Last edited by bitme30 (2009-02-18 21:47:35)
Offline