SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
rtorrent does lots of nice things like watch a folder for new torrents and give a destination to those torrents automatically. Deluge to the same with the autoadd plugin.
I tried the same with qbittorrent and I didn't find a way to do it.
My problem with rtorrent is that my ISP have a restrict QOS or "traffic shaping". I have rtorrent very encrypted (I think!) with this line:
but that limits the max open files and max open sockets. And rtorrent stays "heavy" with lots of torrents. The WebUI wTorrent and even the CLI turns very very slow when the speed reaches 2/3MBytes.
I used Deluge as an option but it crashes a lot. I don't know if it is really that way or if because Slackware or because the great number of torrents.
I have currently about 400 torrents downloading and seeding.
Here is another vote for transmission. It is light on system resources and works very well. It is also updated very frequently. It is very easy to install and use and keep up to date with the slackbuild script at slackbuilds.org.
For what it's worth, transmission is the default torrent app included with the lightweight Slackware based distros Zenwalk and Salix. Transmission is also the default torrent app included with Ubuntu.
@Bruce Hill
I found that aria2 is published under GNU GPL but is featured with xml-rpc which itself is US patented - don't know what to think about that.
The first one I used was transmission but I quickly changed it for rtorrent cause it gives more info about leech and seed.
Now I changed my distro and Im using slackware.
So the default client is ktorrent, and I use it.
With screen you may run rtorrent in background - I think it is a bit more complicated but manual for screen is so huge and discouraging that I never even tried to learn more than 5% about screen. I am using it for a very simple task.
Last edited by igadoter; 09-07-2010 at 02:04 AM.
Reason: mispriniting
I personally prefer transmission. I have it working great in 13.1 x64. I was able to build transmission-2.01 against libevent-1.4.14b-stable (the only dependency). Let me know if you need more info.
Did you link to libevent via flags put along the ./configure? I thought I had libevent installed properly so that ./configure for transmission would be able to find it, but until I used the flags it was not.
As for rtorrent, I'm actually surprised I have neglected to look for a non-GUI torrent client. Might have to check that out!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.