![]() ![]() To be honest, I'm quite happy with µTorrent right now - it seems to be at least as fast as Transmission, and (more importantly) it works, without having to copy stuff around and reinstall stuff. I'm glad Transmission is free, otherwise I'd be an unhappy camper! Then I tried randomising the port in Transmission, and that didn't do anything (that I could tell) - the transmission was stuck in neutral, as it were. I don't *think* it's an ISP issue - I first set µTorrent to use the same port number, and it worked right away. If you need more information, please let me know. So this is a Transmission issue, not an external or network problem! I downloaded another client (µTorrent 1.6.5), dropped the same magnet link on it, and it's downloading just fine. I'm running Lion (10.7.4) on a brand-new MBP 13", with Transmission 2.61 (build 13407). Nothing else (nothing, I swear!) has changed.ĭisabling the local peer option, enabling/disabling all other options in the peers section of prefs, stopping and restarting Transmission after each setting change (since pausing and restarting the transfers did nothing), none of these work any longer. No uploads, the downloads all stalled, and now when I add a magnet link, I get stuck at the "metadata needed" stage. I was looking in Preferences, and enabled "Use local peer discovery" - then everything just stopped. I had half a dozen torrents downloading, and I was seeding another 10 or so just fine. have fun.I've now struck exactly the same problem. it should work on newer versions as well. I used transmission-daemon version 2.31 (12441) for this. now click on any magnet link and transmission will intercept it and will start it automatically on your remote transmission-daemon. Gconftool-2 -t bool -s /desktop/gnome/url-handlers/magnet/enabled true Gconftool-2 -s /desktop/gnome/url-handlers/magnet/needs_terminal false -t bool Gconftool-2 -t string -s /desktop/gnome/url-handlers/magnet/command "/path/to/your/script/from/above/magnetLinkTransfer.sh %s" The last thing you need to do is tell your system what to run when you click on a magnet link. SESSID=$(curl -silent -anyauth -user $USER:$PASS " | sed 's/.*//g s/.*//g')Ĭurl -silent -anyauth -user $USER:$PASS -header "$SESSID" " -d "" ![]() # set true if you want every torrent to be paused initially # NOTE: I had issues using passwords with semicolons ( ) in them, Then you need a little script that calls the ajax function the web interface provides to ‘upload’ the magnet link. this kind of comfort was missing with the remote version of transmission. When you are running a torrent client directly on the machine you pick out your torrents clicking on the magnet link will most likely start the download immediately without having to copy that link. this is very handy since you don’t need to handle any. torrent file (to your remote machine) or just an URL of a torrent or most recently a magnet link. The web interface provides a nice mask to setup your torrents. Since my working machine is not always running but my server is, this is where transmission is set up. Note: if you are running gentoo or a system that uses the xdg-utils with xdg-open, you might want to look at this howto. therefor it even offers a nice looking web interface. it has a nice simple interface and can even be run as a daemon on a server. I’m using transmission for my regular bittorrent needs.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |