Slashdot Mirror

Actually, it supports downloading from magnet links just fine, just not seeding the .torrent file. See this old ticket: http://libtorrent.rakshasa.no/ticket/2100.

rtorrent is popular with remote seedbox sites, easy enough to run on your own system at home on very low-spec hardware. If you compile with rutorrent support, you can admin it with a web browser. I prefer just to ssh into mine and run with the CLI, but the GUI screenshots look slick enough.

1. Install rtorrent
2. Use bash script from here.
3. Copy .torrent files to watch folder

I use bittorrent (transmission) client for download.

rtorrent doesn't need X. Start it in screen and only run X when you need to manage it. To control rtorrent there's plenty of frontends.

Most Bittorrent clients support throttling without any external means. rtorrent, for example, has a maximum bandwidth use setting that is by default disabled, but can be set fairly low.

I remember the SD days when I could just plug analog cable into any device and it Just Worked. I paid them money, month after month. I grumbled that they kept raising the price, but it all worked so conveniently well, that I kept doing it for many years.

That's the minimum standard of functionality. That's what I had, the burden isn't on me to make their stuff work to at least 1980s tech levels, and the customer is always right.

Get back to me when someone releases CableCard drivers for Linux.

Until I can plug digital cable into my unencrypted QAM tuner and have it Just Work, here are the cable TV drivers that I use, and they work nearly as well as the old stuff.

You can wave money in their face, but you can't make them accept it. I don't know why they don't want money, but I'll respect their wishes until they re-open for business. I wish everyone else would do the same.

Are there any particular features that you particularly want uTorrent for, or are you just wanting it because you are already familiar with it in a Winwos environment?

There are a great many Linux native clients you could chose from and while many are text based (which might not be your cup of tea), such as the excellent rtorrent which I tend to use, there are quite a few that are GUI based, of which deluge seems very popular, or are GUI wrappers for working with text based clients (there are several such wrappers for the basic clients, and for recent rtorrent versions too.

Some offer web-based interfaces too, which some find handy if they download to an external machine to reduce the impact on bandwidth quotas and traffic shaping that may be imposed by their ISP.

See this page for a list of clients that you might want to look into.

My requirements were prioritizing, selective downloading, FOSS, a small footprint, and running as service/daemon, and I tried most of the clients on the Wikipedia list that fit these criteria. I liked Deluge most, though I still had a a few problems.

In the end, the problem solved itself when I did the switch from Windows to Linux as my main OS. I use rTorrent, daemonized in screen now and have never looked back. It's very small and has console and (optional) web interfaces.

Oh, and please don't tell anyone I said "FOSS-software".

I wonder if logging IP addresses from bit-torrent clients on a personal computer would be illegal under this ruling.
And some people write some damn good bit-torrent clients :-) Thank you for the great program

They already made a native version for linux.

rtorrent watching a directory for .torrent would be the way to go. And then use unison to keep the .torrent directory in-sync.

rtorrent

Well, if bloat is your issue then I've found the Linux command line client rTorrent to be my personal favorite. When I'm going to be seeding something for the long term (like the new Fedora version that just came out) I'm usually doing so in rTorrent running in a detached screen. That way I don't have to keep my Windows box running 24/7 just to seed something.

As far as GUI clients though I've always been partial to Azureus. To each their own I guess.....

tvrss + pytvshows + rtorrent = Tivo for me.

I work second so it's not like I notice anyway, everything is done by time I get home. All over the waves stuff anyway. I just count it as someone else does the recording and encoding for me.

Real men use rtorrent.

And yes, it supports scheduled throttling and many other common tasks.

Real men use rtorrent.

And yes, it supports scheduled throttling and many other common tasks.

MOC and rTorrent, although I can only vouch for rTorrent.

I second this, and my process is now automagic now that I've spent some time learning rtorrent config AND I finally found a linux cronnable RSS parser.

pytvshows
To
rtorrent
(Read the Common Tasks page to see how to have it move movies/TV shows to their own folder and set up different watch folders)

Plus XBMC having the destination directory as a source and as soon as TV shows are done they pop up.

I second this, and my process is now automagic now that I've spent some time learning rtorrent config AND I finally found a linux cronnable RSS parser.

pytvshows
To
rtorrent
(Read the Common Tasks page to see how to have it move movies/TV shows to their own folder and set up different watch folders)

Plus XBMC having the destination directory as a source and as soon as TV shows are done they pop up.

I find your 0-2% CPU usage estimate for Azeurus hard to reconcile with my own experience, which is more like 15-30% (of course, this depends on how many torrents are open). The only torrent client I've used that has been in the <2% range is rtorrent. When I use ktorrent, which is a native KDE app, I get about 15% CPU usage, so I would guess that a Java app like Azureus would be on par or worse than that. A quick google search brought up some pages where users are complaining about Azureus CPU usage of 60% and up.

IMHO, bittorrent should be able to run in text mode. A GUI is not just unnecessary bloat, but makes it harder to run the client on a remote server. RTorrent is a nice textmode client written for unix, so it probably compiles on OSX too.

Give slackware booting to runlevel 3, gnu screen, gnu coreutils, vim, lynx/links/w3m/elinks, lftp, rtorrent, and moosic a try. There are many others of course.

For torrents I have become quite a fan of rtorrent [ http://libtorrent.rakshasa.no/ ]

It's both fast and very light-weight!

My favourite bittorrent client is rTorrent

"rtorrent is a BitTorrent client for ncurses, using the libtorrent library. The client and library is written in C++ with emphasis on speed and efficiency, while delivering equivalent features to those found in GUI based clients in an ncurses client."

Thanks, man!

That, added to the recent addition of XMLRPC, makes rtorrent just perfect.

Set up a session directory (session directive in the config file.. check the man page) and it will cache all that info. If it doesn't exit cleanly it will still have to rehash though.
There are some scripts on the website for starting rtorrent using init, and likewise, shutting it down via init so you always get a clean shutdown.
Both of these are covered on the Common Tasks section of the website, great resource:
http://libtorrent.rakshasa.no/wiki/RTorrentCommonT asks

--Glenn

get rtorrent
http://libtorrent.rakshasa.no/

with adsl2+ i could get >1meg/s with hundreds of connections, totally stable and only used around ~1%cpu time on a p3 933.

use gentoo and -O3 it too.

screen rtorrent

ssh youraddress

screen -r -x

My favorite client has a bug in it that has caused it to be banned from some private trackers.

Yes, it is true that there is a "User Agent" field in the bit torrent protocol, but of course this is easy to modify. My favorite client has a bug in it that has caused it to be banned from some private trackers. Since this was hurting me on some files that I download, I modified the user agent string to cause the client to identify itself as uTorrent 1.6. Problem solved!

I think that the user agent field is fixed width, meaning that even if you don't have access to the source code to your client, an ambitious user could just change the string in the binary itself.

This is yet another attempt to curtail my rights online. Azureus has sold its soul to the content mafia and is attempting to destroy the Bittorrent community. Utorrent has also sold out to Hollywood fascists. The way I see it, corporate software is the problem here. Do you ever notice native Linux torrent clients don't have this problem? Thank the gods for *nix torrent clients, like rTorrent and Deluge. If you're still on Winblows, sorry charlie. That's what happens when you let Micro$oft and other proprietary Nazis on your box. To all the corporate whores who want a piece of my upload bandwidth to further your goals of DRM, I say "Fuck you". Fuck co-optation and selling out; your infected files will go straight to /dev/null, assholes.

For *nix boxen, you can always use rtorrent http://libtorrent.rakshasa.no/ which is opensource and concentrates on high performance. It has an console only ncurses GUI, but I'm absolutely hooked on it because it is pretty feature rich and fairly easy to grasp. From the site: "LibTorrent is a BitTorrent library written in C++ for *nix, with a focus on high performance and good code. The library differentiates itself from other implementations by transfering directly from file pages to the network stack. On high-bandwidth connections it is able to seed at 3 times the speed of the official client." Screw utorrent's beta WebUI, the crappy azureus remote or setting up a bunch of stuff for torrent flux, screen + rtorrent over ssh is simply an unbeatable combination and anyone running a *nix box should look into it, I'm hooked on it and wouldn't use anything else. BTW it has no relation to the libtorrent on sourceforge.

it's all you need!

Rtorrent is by far the torrent client with the smallest footprint.

I tried them all to get one that worked on a 486 with 60MB RAM and no X. Rtorrent (with ncurses ui) was the only one that didn't max out the resources.

Now I can turn my 4Ghz energy hog off at night, and do my downloading on the 486, which uses about as much electricity as a light bulb.

(For ed2k on the same machine I use mldonkey.

libtorrent with the rtorrent front-end. http://libtorrent.rakshasa.no/

the core implementation is in python of all things, not so tiny.

Get a life man. protocol != implementation.

There are BT protocol implementations in C, C++ and Java.

Small binary size != Fast program

uTorrent != Open Source

uTorrent isn't the fastest torrent program around either, and neither does it have the most features. It probably doesn't strike the best balance either.

Next time you get the "uTorrent is b3tt4r!" bull from the #footorrents channel, read the "only 6mb memory requirement" or the "170KB binary size statistics: consider the fact that uTorrent is missing lots of features, isn't FOSS, depends on an OS with a circa 256mb base requirement, and isn't as fast or as nice with IO as some other clients.

Then perhaps later, consider that the hallmarks of a good program aren't good benchmarks, but good design. The fact that Debian comes on seven cdroms and with 18,000 programs doesn't mean that WinXP is faster because it only comes on one.

Or rtorrent with screen, for a nicer GUI.

rTorrent

Light and resonably featureful.

it's your lucky day. rtorrent is written around a very nice C++ library (hence the site name), so you can even hack your own client pretty easily if you don't like that one. and it's really easy on the resources a vast improvement over all the python crazyness (i won't even mention azureus' java `magic'). highly recommended for console junkies. combine that with screen and you have yourself a fucking textual party. also for quick and dirty jobs i've had good experiences with ctorrent.

disclaimer: yes i am a rtorrent fanboi, but on Windows uTorrent remains king.

Link.

And another vote for rtorrent. I have it running in a (detached) screen session always, monitoring my torrents directory for new files. Sometimes I forget it's even running. :)

check out rtorrent, its an ncurses bittorrent cient with support for downloading and seeding multiple torrents, has down/up rate limiting, a nifty fast resume feature and the ability to select which files within a torrent you want to download. Also has a "pure seeding" mode where it will just seed your torrents. Its pretty cool and runs nicely in screen. You can set up default settings in ~/.rtorrentrc and they have an example one in their wiki. The only thing i miss about azureus is safepeer and texting me when the torrents have finished.

uTorrent is inferior to rTorrent, IMO. rtorrent generally beats uTorrent on performance (try using some of the performance improvements documented on the performance tuning page. It's also open, free, and runs on unix. I haven't personally seen a client that I like more.

Beat that.

I'd recommend something like rTorrent or even the original BitTorrent for both robustness and low resource usage. CLI torrent programs will always be far less resource-intensive than a full-blown GUI like the non-free Windows ones or other popular programs like Azureus.

http://libtorrent.rakshasa.no/
best client out there. curses! nuff said.

http://libtorrent.rakshasa.no/

Santa did try, but he ended up like this. I fear christmas will need to be canceled.

"Ok listen up people, I have had 40 pm's today regarding Bit Comet Ver 0.60 being banned, hear are the answers to all your questions, (a miniature FAQ)

1. Yes it is banned.
2. No, only VER 0.60, all other versions are fine at the moment.
3. If We decide to ban other version we will let you know.
4. No only Bit comet Ver 0.60 is being banned today, so continue to use what you are already using, unless its Bit comet Ver 0.06"

but whatever, i just use http://libtorrent.rakshasa.no/ anyways (curses yay!)

If you want a CLI tool for seeding, you could try libTorrent. It works great, uses little memory and is free