the forums at degreez.net http://forums.degreez.net/ |
|
Linux question ./btdownloadcurses.py options in command http://forums.degreez.net/viewtopic.php?f=3&t=336 |
Page 1 of 1 |
Author: | twiley [ Mon Apr 05, 2004 7:27 am ] |
Post subject: | Linux question ./btdownloadcurses.py options in command |
Sorry to ask this but I have not seen a post about this so here goes. when I view these options. --max_uploads <arg> the maximum number of uploads to allow at once. (defaults to 7) --keepalive_interval <arg> number of seconds to pause between sending keepalives (defaults to 120.0) --download_slice_size <arg> How many bytes to query for per request. (defaults to 16384) --request_backlog <arg> maximum number of requests to keep in a single pipe at once. (defaults to 10) --max_message_length <arg> maximum length prefix encoding you'll accept over the wire - larger values get the connection dropped. (defaults to 8388608) --ip <arg> ip to report you have to the tracker. (defaults to '') --minport <arg> minimum port to listen on, counts up if unavailable (defaults to 6881) --maxport <arg> maximum port to listen on (defaults to 6999) --responsefile <arg> file the server response was stored in, alternative to url (defaults to '') --url <arg> url to get file from, alternative to responsefile (defaults to '') --saveas <arg> local file name to save the file as, null indicates query user (defaults to '') --timeout <arg> time to wait between closing sockets which nothing has been received on (defaults to 300.0) --timeout_check_interval <arg> time to wait between checking if any connections have timed out (defaults to 60.0) --max_slice_length <arg> maximum length slice to send to peers, larger requests are ignored (defaults to 131072) --max_rate_period <arg> maximum amount of time to guess the current rate estimate represents (defaults to 20.0) --bind <arg> comma-separated list of ips/hostnames to bind to locally (defaults to '') --ipv6_enabled <arg> allow the client to connect to peers via IPv6 (defaults to 0) --ipv6_binds_v4 <arg> set if an IPv6 server socket will also field IPv4 connections (defaults to 0) --upload_rate_fudge <arg> time equivalent of writing to kernel-level TCP buffer, for rate adjustment (defaults to 5.0) --display_interval <arg> time between updates of displayed information (defaults to 0.5) --rerequest_interval <arg> time to wait between requesting more peers (defaults to 300) --min_peers <arg> minimum number of peers to not do rerequesting (defaults to 20) --http_timeout <arg> number of seconds to wait before assuming that an http connection has timed out (defaults to 60) --max_initiate <arg> number of peers at which to stop initiating new connections (defaults to 40) --check_hashes <arg> whether to check hashes on disk (defaults to 1) --max_upload_rate <arg> maximum kB/s to upload at, 0 means no limit (defaults to 0) --alloc_type <arg> allocation type (may be normal, background, pre-allocate or sparse) (defaults to 'normal') --alloc_rate <arg> rate (in MiB/s) to allocate space at using background allocation (defaults to 2.0) --snub_time <arg> seconds to wait for data to come in over a connection before assuming it's semi-permanently choked (defaults to 30.0) --spew <arg> whether to display diagnostic info to stdout (defaults to 0) --rarest_first_cutoff <arg> number of downloads at which to switch from random to rarest first (defaults to 2) --rarest_first_priority_cutoff <arg> the number of peers which need to have a piece before other partials take priority over rarest first (defaults to 3) --min_uploads <arg> the number of uploads to fill out to with extra optimistic unchokes (defaults to 4) --max_files_open <arg> the maximum number of files to keep open at a time, 0 means no limit (defaults to 50) --round_robin_period <arg> the number of seconds between the client's switching upload targets (defaults to 30) --super_seeder <arg> whether to use special upload-efficiency-maximizing routines (only for dedicated seeds) (defaults to 0) --security <arg> whether to enable extra security features intended to prevent abuse (defaults to 1) --max_connections <arg> the absolute maximum number of peers to connect with (0 = no limit) (defaults to 0) --auto_kick <arg> whether to allow the client to automatically kick/ban peers that send bad data (defaults to 1) --double_check <arg> whether to double-check data being written to the disk for errors (may increase CPU load) (defaults to 1) --triple_check <arg> whether to thoroughly check data being written to the disk (may slow disk access) (defaults to 0) --lock_files <arg> whether to lock files the client is working with (defaults to 1) --lock_while_reading <arg> whether to lock access to files being read (defaults to 0) I have no idea what all those options do but these. --max_uploads <arg> the maximum number of uploads to allow at once. (defaults to 7) --saveas <arg> local file name to save the file as, null indicates query user (defaults to '') --max_upload_rate <arg> maximum kB/s to upload at, 0 means no limit (defaults to 0) This one I know what it does but when I use this option I get an error. --super_seeder <arg> whether to use special upload-efficiency-maximizing routines (only for dedicated seeds) (defaults to 0) --max_upload_rate <arg> maximum kB/s to upload at, 0 means no limit (defaults to 0) --max_connections <arg> the absolute maximum number of peers to connect with (0 = no limit) (defaults to 0) Some kinda give me the idea but I am still lost. For example what does this mean? --round_robin_period <arg> the number of seconds between the client's switching upload targets (defaults to 30) Sorry I am new to linux but been using Shadows client for a long time now. What I really want to do here is Have the client report back to the tracker every 5 mintues so my stats are updated. Get the error message in super seed mode not to appear and to have the client stay connected to the tracker. I notice when I am on a multi tracker torrent my client drops off if the main tracker is down and the torrent is running on a back up tracker. here is the command I use for regular torrent download. ./btdownloadcurses.py /home/twiley/torrent/GD7-19-94SBD.torrent --saveas /home/twiley/shn/ --max_upload_rate 15 when I am in super seed mode this is what I use. ./btdownloadcurses.py /home/twiley/torrent/GD7-19-94SBD.torrent --saveas /home/twiley/shn/ --max_upload_rate 15 --super_seeder 1 the error I get is this... Thanks for any info. twiley |
Author: | TheSHAD0W [ Mon Apr 05, 2004 12:34 pm ] |
Post subject: | |
Actually, super-seed posts an informational error message. That client may be live, and just not connected to anyone yet. |
Author: | twiley [ Mon Apr 05, 2004 8:26 pm ] |
Post subject: | |
OK cool so the error(s) is just a generic message. So how do I have the client report back to the tracker every 5 mintues so my stats are updated? What command can I add to this to have the client do that every 5 mintues? This is what I am using currently. ./btdownloadcurses.py /home/twiley/torrent/GD7-19-94SBD.torrent --saveas /home/twiley/shn/ --max_upload_rate 15 Which command and at what # setting would I use? Thanks for the timely response on the super seed mode I really do appreciate it twiley |
Author: | TheSHAD0W [ Tue Apr 06, 2004 9:31 am ] |
Post subject: | |
The client already reports to the tracker as necessary, automatically. That command-line option is just fine. |
Page 1 of 1 | All times are UTC - 7 hours [ DST ] |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |