:xxxxx**
+ This is the ip reported to the tracker.
+ It should be the same as the ip from where you are browsing the tracker.
+
+**Bind: xxx.xxx.xxx.xxx**
+ This is the ip on which libtorrent/rtorrent is running.
+ The external ip if you're behind a NAT.
+
+**[D 15/0]**
+ Current number of download slots in use and the maximum (0 if unlimited).
+
+**[H 1/32]**
+ Current number of active HTTP requests (for tracker announces and downloads of .torrent files), and the maximum.
+
+**[U 3/14]**
+ Current number of upload slots in use, and the maximum, which depends on the global upload rate limit.
+
+**[S 6/40/768]**
+ The three numbers represent handshakes/open sockets/max open sockets.
+
+**[F 4/128]**
+ The two numbers represent open files/max open files. The library dynamically closes the least used files as needed.
+
+## The Peers screen ##
+
+Some parts of this screen is fairly cryptic, here's an explanation of the fields.
+
+Header:
+```
+IP UP DOWN PEER C/RE/LO QS DONE REQ SNUB
+```
+Example entry:
+```
+1.1.1.1 1.1 0.0 20.5 r/ci/un 3/0 32
+```
+
+
+###Explanation###
+
+**IP**
+ The IP address of the peer. (Which, of course, has nothing to do with DNS)
+
+**UP**
+ The rate at which your client is uploading to the peer (KiB/sec).
+
+**DOWN**
+ The rate at which your client is downloading from the peer (KiB/sec).
+
+**PEER**
+ The download rate (KiB/sec) of this peer for this torrent (reported to your client by the peer client).
+
+**C/RE/LO**
+C = Connection type, can be r, l, R or L.
+ r = Started remotely, the peer initiated the connection to your client.
+ l = Started locally, your client initiated the connection to the peer.
+ R = Started remotely, using encrypted data transfer.
+ L = Started locally, using encrypted data transfer.
+
+RE = Remote client information, has two parts; the first is u or c and the second is i or n.
+ c = This peer has choked your client (which means it is not going to send you any pieces for now).
+ u = Your client is not choked by this peer (unchoked).
+ i = This peer is interested in downloading from your client.
+ n = This peer is not interested in downloading from your client.
+ LO = Local client information, has two parts; the first is u or c and the second is i or n.
+ c = Your client has choked this peer (which means it is not going to send this peer any pieces for now).
+ u = Your client is not choking the peer (unchoked).
+ i = Your client is interested in downloading from this peer.
+ n = Your client is not interested in downloading from this peer.
+
+**QS**
+Queues Outoing/Incoming pieces.
+The first is the number of pieces that are queued to be sent to the peer.
+The second is the number of pieces your client has requested and is waiting for the peer to send.
+
+**DONE**
+What percent this peer has of the file.
+
+**REQ**
+The number of the piece that is currently on the top of the request queue.
+
+**SNUB**
+This field has a * in it when your client is snubbing this peer. When a peer agrees to send you a piece you have requested and then does not send that piece within a certain time your client will snub this peer. It is basically a way for the client to flag that this peer is unreliable and it is better to request pieces from other clients.
+
+###Status###
+
+A status line in this screen lists information such as:
+```
+Peers: 99(1002) Min/Max: 40/100 Uploads: 15 U/I/C/A: 3/71/5/3 Failed: 0
+```
+**Peers**
+ The amount of peers you are connected and (not connected) to.
+
+**Min/Max**
+ The minimum and maximum amount of peers to try to keep connected. Can be toyed with keys 3, 4, 5 and 6.
+
+**Uploads**
+ Maximum number of peers to upload to at the same time (given the global upload slots are available). Can be toyed with keys 1 and 2.
+
+**U/I/C/A**
+U = Number of corrently unchoked peers
+I = Currently interested peers
+C = Complete peers
+A = Peers accounted
+
+**Failed**
+Number of failed chunks.
+
+## The Chunks seen screen ##
+
+ Chunks seen: [C/A/D 25/29/6.99] X downloaded X missing X queued X downloading
+ 0 EFDFEFFDFE CEFFFFFFFF EFCFCFDDBC 9DFDBDDECF BDDBCEDDFD DEFEEDECFC
+ 60 DBDFEE9BEC FCCBECCFEB FAFDDFCAAD CABCDECDFC 9BFDCDEFAA ADCEFFBBDC
+ 120 FAFFCCBEAC EDFFEDDF9B EDD9DEBDDD C9BCEAFF9C F8FDCDDBFB CFCECFCEDD
+ 180 FFFADCCFAE FB9FBFCCAC BEABBB9FDD ABCECEDFAB DCF9BDDFBD BBEFAE7EED
+ 240 DDCEAFBCF7 EEEFBF9AAD 9FDBCDDEBB DDF79C8FCE EFF9FDFE9A EF9DCCEEBA
+
+
+
+
+C/A/D stands for Complete/Accounted/Distributed copies. Only those peers whose bitfields are accounted for are included above; they do not include seeders, peers with empty bitfields, nor normal peers if there are too many.
+
+Then, you have a view of the chunks of the torrent. The chunks are shown in groups of 10. Each new line begins with the number of the first chunk on that line.
+
+Each chunk is shown by a hexadecimal number (0123456789ABCDEF) which is equal to its rarity among the non-seeders:
+
+ * a chunk shown as 0 is not available from non-seeders in the swarm (but all seeders have it of course)
+ * a chunk shown as 6 is available from 6 non-seeders
+ * and a chunk shown as F is available from 15 or more peers.
+
+If the chunk is in **bold** it means you do not have that chunk yet, if it is underlined then it is in the transfer list (i.e. queued to be downloaded), and if the chunk is in reverse colors, it is currently being downloaded. Otherwise, a normal font indicates that the chunk has already been downloaded and verified as correct by rTorrent.
+
+
+## Session directory ##
+
+Setting the *session* option will enable session management and the torrent files for all open downloads will be stored in this directory. When restarting rtorrent all torrents previously open will be restored. Only one instance of rtorrent should be used with each session directory, though at the moment no locking is done. An empty string will disable the session directory.
+
+
+## Watching a directory for torrents ##
+
+The client may be configured to check a directory for new torrents and load them. Torrents loaded in this manner will be ''tied'' to the filename and when the file is deleted the torrent may be stopped or removed. If a torrent which is tied to a file is removed from the client, the tied file will be deleted.
+
+```
+schedule = watch_directory,5,5,load_start=./watch/*.torrent
+schedule = untied_directory,5,5,stop_untied=
+```
+
+## Other Miscellaneous Information ##
+
+**Notice: This information might not be up to date.**
+
+### Manually setting the local IP ###
+
+Using the ''-i '' flag or ''"ip = "'' option you may change your ip address that is reported to the tracker. If you have a dynamic ip address then ''"schedule = ip_tick,0,1800,ip=my_address"'' may be used to update the ip address every 30 minutes.
+
+The client may spend as much as 60 seconds trying to contact a UDP tracker, so if you are behind a firewall that blocks the reply packets you should tell the client to skip the UDP tracker. Set "use_udp_trackers = no" in your configuration file or in the command line option.
+
+### Signal handlers ###
+
+|||
+| ------------- | ------------- |
+| SIGINT | Normal shutdown with 5 seconds to send the stopped request to trackers. |
+| SIGTERM | Shut down immediately. |
+| SIGWINCH | Resize and redraw. |
\ No newline at end of file