If you look around on the forums for WL-500gP you can find the transmission.cgi, albeit modded versions which are even nicer.
There are .conf files around as well probably...
I had the bad idea to do ipkg update && ipkg upgrade today and I found out that transmission is not working anymore.
It seems that transmission.conf, the cgi script and the watchdog disappeared.
The previous version 1.22 does not exist anymore on http://ipkg.nslu2-linux.org/feeds/op.../cross/stable/
What can I do ?
If you look around on the forums for WL-500gP you can find the transmission.cgi, albeit modded versions which are even nicer.
There are .conf files around as well probably...
transmissiond ( the daemon) is not there either.
I renamed transmission-daemon to transmissiond, but it doesn't works.
I've also get the transmission-watchdog, transmission.cgi from the svn (version 1.22), but they doesn't work with 1.31
That old stuff doesn't work with 1.31 because transmission now uses other methods (JSON) for communication. Use transmission-daemon with the bundled web-ui or the transmission-remote command. Read man for the daemon as theer are many new options now, for example authentication.
But 1.31 had a big bug so private trackers banned it. So now 1.32 is out. Would be nice with new optware package
Can anyone upload somewhere the 1.22 ipk ?
Did the same thing, but launch "transmission-daemon" and browse to http://localhost:9091. Here you have prefs and the (web)-GUI is much better then 1.22.
/flake
Thank you xflake
How do you resume the torrents you were seeding?
And how do you start to download a new torrent?
And how do you launch "transmission-daemon"?
right...
I did launch the stuff (done in putty, just type "transmission-daemon" and hit enter)
then I went to the interface at the new port 9091... and I get a link to somewhere but it doesnt take me anywhere, it just keeps waiting:S
It works for me
http://routerIP:9091/transmission/web/
Daemon has a few nice switches
Options:
-h --help Display this help page and exit
-a --acl <list> Access Control List. (Default: +127.0.0.1)
-b --blocklist Enable peer blocklists
-B --no-blocklist Disable peer blocklists
-f --foreground Run in the foreground instead of daemonizing
-g --config-dir <path> Where to look for configuration files
-p --port <port> RPC port (Default: 9091)
-t --auth Require authentication
-T --no-auth Don't require authentication
-u --username <username> Set username for authentication
-v --password <password> Set password for authentication
-w --download-dir <path> Where to save downloaded data
But - how to move old source, work and target directories to 1.32?
Here is my experience with this new beauty after 9 hours of testing. I have upgraded my transmission to 1.31 late last night and I have to confess, I was blown away by the features right after the magical ipkg update && ipkg upgrade.
First off all, the modern web 2.0 look fits in nicely and honestly this is what I have been waiting for. It's simply great. I can't wait to get more aquainted with it, and who knows, maybe add a feature or two to it.
Secondly, the pressure and work load put on Asus is much lesser compared to the previous 1.22 version. I was trying to download a 16GB torrent with 1.22 and Asus couldn't handle it properly. Even with swap on an external usb hdd, sysload was averaging about 2 and speeds weren't too good. However, after the update sysload decreased to 1.1 whereas speeds got roof high, which means even with huge torrents Transmision is maxing out my connection (4mbit). I'm not so sure about any changes in CPU and memory usage. I believe they haven't changed noticeably.
That's it for now. All in all, guys at transmissionbt did a great job once again.
P.S. If you want daemon to start automatically, you can add it to post-boot script.
P.S.2 There is no other way to resume you previous downloading or seeding torrents instead of just moving directories from work to transmission 1.31+ download dir and then starting the correspondent .torrent files. I'm pretty sure they will get recheked and started again.
I apologie for another post. Though here is a screenshot of how it looks like to those, who still hesitate whether or not to upgrade. http://img401.imageshack.us/img401/8710/tr131zy1.jpg
The setup is even more full-proof as there is no more a need for httpd to run web interface. Transmission-daemon comes with its own. This is definetely easier to setup.
On the downside, however, new AJAX interface and transmission-daemon lacks couple of handy features that existed in previous version (1.22, at least). Main thing that it lacks is, a queue system. Right now torrent gets started as soon as added, because there is no option to control the number of active torrents. Traffic/sysload graph is also missing.
Last edited by GoldDigger; 10-08-2008 at 09:07.
what the configuration file of this new transmission? And how do I do run at?
1.32 is out and is accepted by some private trackers.
I managed to resume seeding torrents by moving the files existing in
/tmp/harddisk/torrent/.config/transmission/resume
and
/tmp/harddisk/torrent/.config/transmission/torrents
to
/tmp/local/root/.config/transmission-daemon/resume
and
/tmp/local/root/.config/transmission-daemon/torrents
and restarting transmission-daemon.
I did not have currently downloading torrents, but I think it should work in the same way.
that helped me out a bit, now I did this:
well... it now linked me forward and guess what!transmission-daemon -p 8008 -w /mnt/torrent -a 192.168.2.
look at the screenshot... not supported browser
whaat? they support every other browser apart from IE that is being used more than anything...... it doesnt make that big difference I think, the only trouble IE has is with some java based sites, but something plain looking like I saw on the screenshot posted here should be handeled by IE easily
I guess it's time for me to go and look for a different torrent client