From 3c18f164ab3e556a6bc70e03b7544b5a1ae0d780 Mon Sep 17 00:00:00 2001 From: Arvid Norberg Date: Fri, 12 Jun 2009 16:41:44 +0000 Subject: [PATCH] regenerated html documentation --- docs/manual.html | 764 +++++++++++++++++++++++++++++++++++++++------ docs/projects.html | 2 +- docs/tuning.html | 6 +- 3 files changed, 676 insertions(+), 96 deletions(-) diff --git a/docs/manual.html b/docs/manual.html index dd56415bd..70f27b7f7 100644 --- a/docs/manual.html +++ b/docs/manual.html @@ -201,74 +201,85 @@
  • scrape_failed_alert
  • url_seed_alert
  • hash_failed_alert
    • -
  • peer_ban_alert
    • -
  • peer_error_alert
    • -
  • invalid_request_alert
    • -
  • torrent_finished_alert
    • -
  • performance_alert
    • -
  • state_changed_alert
    • -
  • metadata_failed_alert
    • -
  • metadata_received_alert
    • -
  • fastresume_rejected_alert
    • -
  • peer_blocked_alert
    • -
  • storage_moved_alert
    • -
  • storage_moved_failed_alert
    • -
  • torrent_paused_alert
    • -
  • torrent_resumed_alert
    • -
  • save_resume_data_alert
    • -
  • save_resume_data_failed_alert
    • -
  • dht_announce_alert
    • -
  • dht_get_peers_alert
    • -
  • dispatcher
    • +
  • peer_alert
    • +
  • peer_ban_alert
    • +
  • peer_snubbed_alert
    • +
  • peer_unsnubbed_alert
    • +
  • peer_error_alert
    • +
  • peer_connected_alert
    • +
  • peer_disconnected_alert
    • +
  • invalid_request_alert
    • +
  • HTTP/1.1 200 OK Set-Cookie: i_like_gitea=e9088f7aa2a1c88c; Path=/; HttpOnly; Secure; SameSite=Lax Set-Cookie: _csrf=AepwXR6WESY9jYwzaNcXTHcz6BA6MTc1MzI2ODQ0Nzg1NzU0MTg4Ng; Path=/; Max-Age=86400; HttpOnly; Secure; SameSite=Lax X-Frame-Options: SAMEORIGIN Date: Wed, 23 Jul 2025 11:00:47 GMT Content-Type: text/plain; charset=utf-8 Connection: close Transfer-Encoding: chunked Cache-Control: max-age=0, private, must-revalidate, no-transform X-Cache-Status: HIT X-Cache-Age: 0 8000 From 3c18f164ab3e556a6bc70e03b7544b5a1ae0d780 Mon Sep 17 00:00:00 2001 From: Arvid Norberg Date: Fri, 12 Jun 2009 16:41:44 +0000 Subject: [PATCH] regenerated html documentation --- docs/manual.html | 764 +++++++++++++++++++++++++++++++++++++++------ docs/projects.html | 2 +- docs/tuning.html | 6 +- 3 files changed, 676 insertions(+), 96 deletions(-) diff --git a/docs/manual.html b/docs/manual.html index dd56415bd..70f27b7f7 100644 --- a/docs/manual.html +++ b/docs/manual.html @@ -201,74 +201,85 @@
  • scrape_failed_alert
  • url_seed_alert
  • hash_failed_alert
    • -
  • peer_ban_alert
    • -
  • peer_error_alert
    • -
  • invalid_request_alert
    • -
  • torrent_finished_alert
    • -
  • performance_alert
    • -
  • state_changed_alert
    • -
  • metadata_failed_alert
    • -
  • metadata_received_alert
    • -
  • fastresume_rejected_alert
    • -
  • peer_blocked_alert
    • -
  • storage_moved_alert
    • -
  • storage_moved_failed_alert
    • -
  • torrent_paused_alert
    • -
  • torrent_resumed_alert
    • -
  • save_resume_data_alert
    • -
  • save_resume_data_failed_alert
    • -
  • dht_announce_alert
    • -
  • dht_get_peers_alert
    • -
  • dispatcher
    • +
  • peer_alert
    • +
  • peer_ban_alert
    • +
  • peer_snubbed_alert
    • +
  • peer_unsnubbed_alert
    • +
  • peer_error_alert
    • +
  • peer_connected_alert
    • +
  • peer_disconnected_alert
    • +
  • invalid_request_alert
    • +
  • 2362 port + +75 +invalid_pad_size +The pad size used in the encryption handshake is of invalid size + +76 +invalid_encrypt_handshake +The encryption handshake is invalid + +77 +no_incoming_encrypted +The client is set to not support incoming encrypted connections +and this is an encrypted connection + +78 +no_incoming_regular +The client is set to not support incoming regular bittorrent +connections, and this is a regular connection + +79 +duplicate_peer_id +The client is already connected to this peer-ID + +80 +torrent_removed +Torrent was removed + +81 +packet_too_large +The packet size exceeded the upper sanity check-limit + +82 +http_parse_error +Failed to parse HTTP response + +83 +http_error +The web server responded with an error + +84 +missing_location +The web server response is missing a location header + +85 +invalid_redirection +The web seed redirected to a path that no longer matches the +.torrent directory structure + +86 +redirecting +The connection was closed becaused it redirected to a different +URL + +87 +invalid_range +The HTTP range header is invalid + +88 +no_content_length +The HTTP response did not have a content length + +89 +banned_by_ip_filter +The IP is blocked by the IP filter + +90 +too_many_connections +At the connection limit + +91 +peer_banned +The peer is marked as banned + +92 +stopping_torrent +The torrent is stopping, causing the operation to fail + +93 +too_many_corrupt_pieces +The peer has sent too many corrupt pieces and is banned + +94 +torrent_not_ready +The torrent is not ready to receive peers + +95 +peer_not_constructed +The peer is not completely constructed yet + +96 +session_closing +The session is closing, causing the operation to fail + +97 +optimistic_disconnect +The peer was disconnected in order to leave room for a +potentially better peer + +98 +torrent_finished +The torrent is finished + +99 +no_router +No UPnP router found + +100 +metadata_too_large +The metadata message says the metadata exceeds the limit + +101 +invalid_metadata_request +The peer sent an invalid metadata request message + +102 +invalid_metadata_size +The peer advertised an invalid metadata size + +103 +invalid_metadata_offset +The peer sent a message with an invalid metadata offset + +104 +invalid_metadata_message +The peer sent an invalid metadata message + +105 +pex_message_too_large +The peer sent a peer exchange message that was too large + +106 +invalid_pex_message +The peer sent an invalid peer exchange message + +107 +invalid_lt_tracker_message +The peer sent an invalid tracker exchange message + +108 +unsupported_protocol_version +The NAT-PMP router responded with an unsupported protocol version + +109 +natpmp_not_authorized +You are not authorized to map ports on this NAT-PMP router + +110 +network_failure +The NAT-PMP router failed because of a network failure + +111 +no_resources +The NAT-PMP router failed because of lack of resources + +112 +unsupported_opcode +The NAT-PMP router failed because an unsupported opcode was sent +

    The names of these error codes are declared in then libtorrent::errors namespace.

    +

    There is also another error category, libtorrent::upnp_category, defining errors +retrned by UPnP routers. Here's a (possibly incomplete) list of UPnP error codes:

    + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    codesymboldescription
    0no_errorNo error
    402invalid_argumentOne of the arguments in the request is invalid
    501action_failedThe request failed
    714value_not_in_arrayThe specified value does not exist in the array
    715source_ip_cannot_be_wildcardedThe source IP address cannot be wild-carded, but +must be fully specified
    716external_port_cannot_be_wildcardedThe external port cannot be wildcarded, but must +be specified
    718port_mapping_conflictThe port mapping entry specified conflicts with a +mapping assigned previously to another client
    724internal_port_must_match_externalInternal and external port value must be the same
    725only_permanent_leases_supportedThe NAT implementation only supports permanent +lease times on port mappings
    726remote_host_must_be_wildcardRemoteHost must be a wildcard and cannot be a +specific IP addres or DNS name
    727external_port_must_be_wildcardExternalPort must be a wildcard and cannot be a +specific port
    +

    The UPnP errors are declared in the libtorrent::upnp_errors namespace.

    translating error codes

    The error_code::message() function will typically return a localized error string, diff --git a/docs/projects.html b/docs/projects.html index 9f947d5ca..199a95296 100644 --- a/docs/projects.html +++ b/docs/projects.html @@ -3,7 +3,7 @@ - + projects using libtorrent diff --git a/docs/tuning.html b/docs/tuning.html index 16ace699f..9755f341d 100644 --- a/docs/tuning.html +++ b/docs/tuning.html @@ -224,16 +224,16 @@ same semantics.

    high performance seeding

    In the case of a high volume seed, there are two main concerns. Performance and scalability. -This transelates into high send rates, and low memory and CPU usage per peer connection.

    +This translates into high send rates, and low memory and CPU usage per peer connection.

    file pool

    libtorrent keeps an LRU file cache. Each file that is opened, is stuck in the cache. The main -purpose of this is because of anti-virus software that hooks och file-open and file close to +purpose of this is because of anti-virus software that hooks on file-open and file close to scan the file. Anti-virus software that does that will significantly increase the cost of opening and closing files. However, for a high performance seed, the file open/close might be so frequent that it becomes a significant cost. It might therefore be a good idea to allow a large file descriptor cache. Adjust this though session_settings::file_pool_size.

    -

    Don't forget to set a high rlimit for file descriptors in yor process as well. This limit +

    Don't forget to set a high rlimit for file descriptors in your process as well. This limit must be high enough to keep all connections and files open.

    0