You are not logged in.

#1 2010-08-02 15:53:31

yabasta
Member
Registered: 2010-05-01
Posts: 167

[solved]seeding with rtorrent

i'm trying to seed a torrent using rtorrent. i can easily do this via deluge but i really want to be able to do all this from the command line.
Here's what i've done so far (hmm, incidentally i've just noticed there's no button for 'code' etc in this new forum software) -

i made the torrent with mktorrent like so :  mktorrent -a http:my.tracker.com -o "name of my torrent" /home/path_to_files_to_torrent
i assume this went well, i got a message saying
'mktorrent 1.0 (c) 2007, 2009 Emil Renner Berthing
Hashed 312 of 312 pieces.
Writing metainfo file... done'

after that i uploaded the .torrent file to where it needed to go, and this is where it probably all goes a bit fuzzy. i was't sure how to get rtorrent to
begin seeding so i placed the .torrent file into the 'watch' directory, which rtorrent regsitered. and then that was that. nothing happened, so i
thought maybe i should put the torrent files into my 'torrents' directory where rtorrent stores the downloaded torrents. still no joy. i can't seem
to find much documentation about actually setting up a seed for rtorrent. any suggestions?

Last edited by yabasta (2010-08-03 17:26:15)

Offline

#2 2010-08-02 15:55:51

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819

Re: [solved]seeding with rtorrent

You need to tell rtorrent to verify the torrent afaik. And make sure the contents are in the directory where rtorrent expects the data.


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#3 2010-08-02 16:21:15

Doehni
Member
From: Germany
Registered: 2007-05-19
Posts: 175

Re: [solved]seeding with rtorrent

yabasta wrote:

hmm, incidentally i've just noticed there's no button for 'code' etc in this new forum software

Just click on BBCode (it's a link) and you're up to the help page with quite a few formating tips. smile Didn't know that either until some days ago...

Offline

#4 2010-08-02 16:54:32

d2ogch3n
Member
Registered: 2010-01-20
Posts: 42

Re: [solved]seeding with rtorrent

Maybe try downloading the torrent from the site you uploaded to as you would normally do. Have the files you want to seed in the directory where they would end up. rTorrent should then hash check the file and start seeding.

Offline

#5 2010-08-02 17:06:59

tjwoosta
Member
Registered: 2008-12-18
Posts: 453

Re: [solved]seeding with rtorrent

I seed with rtorrent all the time.

You can either put the .torrent in the watch directory (if you have one set up in .rtorrent.rc) so it opens automatically or just press enter and load the torrent that way. After the torrent is loaded into rtorrent it should start hash checking on its own, if not press ctrl-r to begin hash checking. After its done hashing it should start seeding on its own, if not press ctrl-s to start the torrent, or ctrl-d to stop it.

All in all you basically just start it the same way you would if you were leeching. It does a hash check to verify that all the data is there then it starts seeding, if all the data is not there it will start leeching instead.

Offline

#6 2010-08-02 17:28:32

yabasta
Member
Registered: 2010-05-01
Posts: 167

Re: [solved]seeding with rtorrent

@ d2ogch3n
that rather defeats the object, sorry

@ tjwoosta
all i do when leeching is to download the .torrent file to my 'watch' directory and it starts itself from there.
if you don't mind to go over once more.....i use mktorrent to make the .torrent file like i mentioned above, only with the torrent's files in their own folder in rtorrents 'torrent' directory. then place the subsequent .torrent file into 'watch' ?

@doehni
thanks for the tip big_smile

Last edited by yabasta (2010-08-02 17:33:10)

Offline

#7 2010-08-02 17:33:45

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819

Re: [solved]seeding with rtorrent

Do you download the torrent file from the tracker first, or did you point rtorrent to the local copy of your torrent file?

Also, did you test another client, like transmission? If both fail, then maybe there's something wrong with your torrent file rather than with the way you try to get it going in rtorrent.


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#8 2010-08-02 19:26:58

yabasta
Member
Registered: 2010-05-01
Posts: 167

Re: [solved]seeding with rtorrent

no, i create the torrent at this end with mktorrent, adding the tracker address then. and yes i made the torrent with deluge and it worked. i create quite a few torrents and i just want to be able to do it all from the command line. deluge creeps up to 100% cpu now and then so i tried rtorrent. 17 meg of ram and very little cpu when downloading sold me on it.

Offline

#9 2010-08-02 19:56:14

Spip
Member
From: USA
Registered: 2010-07-29
Posts: 28

Re: [solved]seeding with rtorrent

I wrote one year ago an article on this wiki
http://wiki.mandriva.com/fr/Early_seede … le_partage
about rtorrent for seeders. However, it is written in french (sorry) but a translator should give you a not so bad translation and commands are really streight forward.

The purpose is to write a daemon which runs rtorrent and detach rtorrent with dtach.

The main advantage compared to transmission is the automatism and at the end of the day, it doesn't need more attention.

I hope it could help you.

Offline

#10 2010-08-02 22:23:39

tjwoosta
Member
Registered: 2008-12-18
Posts: 453

Re: [solved]seeding with rtorrent

yabasta wrote:

@ tjwoosta
all i do when leeching is to download the .torrent file to my 'watch' directory and it starts itself from there.
if you don't mind to go over once more.....i use mktorrent to make the .torrent file like i mentioned above, only with the torrent's files in their own folder in rtorrents 'torrent' directory. then place the subsequent .torrent file into 'watch' ?

If by "rtorrents 'torrent' directory" you mean the directory that currently downloading torrents go to then it sounds like you have it right. You put the files that are to be torrented into the same directory that currently active torrents go in while leeching. Depending on how you have rtorrent configured this might not be the same directory that finished downloads end up. It might help to post your .rtorrent.rc so we an see how you have your directories set up.

Also what are contents of the torrent?  Did you add the whole folder to the .torrent or just the files themselves? If you didn't add the whole folder to the .torrent then you don't need to put the files into their own folder for rtorrent.

Offline

#11 2010-08-03 08:28:03

yabasta
Member
Registered: 2010-05-01
Posts: 167

Re: [solved]seeding with rtorrent

yes, i meant the directory of currently downloaded torrents. and my downloaded torrents stay there too.generally my torrents have quite a few files so to keep them tidy i put them all in one directory and point mktorrent at that. anyay, here's my .rtorrent.rc :

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed. Remember to
# uncomment the options you wish to enable.

# Maximum and minimum number of peers to connect to per torrent.
#min_peers = 40
#max_peers = 100

# Same as above but for seeding completed torrents (-1 = same as downloading)
#min_peers_seed = 10
#max_peers_seed = 50

# Maximum number of simultanious uploads per torrent.
max_uploads = 8

# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 0
upload_rate = 30

# Default directory to save the downloaded torrents.
directory = /home/yabasta/torrents

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = /home/yabasta/.session

# Watch a directory for new torrents, and stop those that have been
# deleted.
schedule = watch_directory,5,5,load_start=/home/yabasta/watch/*.torrent
schedule = untied_directory,5,5,stop_untied=

# Close torrents when diskspace is low.
schedule = low_diskspace,5,60,close_low_diskspace=100M

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,"stop_on_ratio=200,200M,2000"

# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
port_range = 6881-6891

# Start opening ports at a random position within the port range.
#port_random = no

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
#check_hash = no

# Set whetever the client should try to connect to UDP trackers.
#use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
# encryption = allow_incoming,enable_retry,prefer_plaintext

# Enable DHT support for trackerless torrents or when all trackers are down.
# May be set to "disable" (completely disable DHT), "off" (do not start DHT),
# "auto" (start and stop DHT as needed), or "on" (start DHT immediately).
# The default is "off". For DHT to work, a session directory must be defined.
# 
# dht = auto

# UDP port to use for DHT. 
# 
# dht_port = 6881

# Enable peer exchange (for torrents not marked private)
#
# peer_exchange = yes

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10

seems to work fine for me

and thanks spip, i'll look into thtat later when i have time

Last edited by yabasta (2010-08-03 08:30:20)

Offline

Board footer

Powered by FluxBB