A clone of btpd with my configuration changes.
No puede seleccionar más de 25 temas Los temas deben comenzar con una letra o número, pueden incluir guiones ('-') y pueden tener hasta 35 caracteres de largo.

163 líneas
5.2 KiB

  1. btpd 0.13:
  2. ----------
  3. Misc:
  4. - cURL is no longer required. btpd now uses its own http client.
  5. - btpd doesn't use threads anymore, so pthreads are not required.
  6. - Needed parts of libevent are now included in btpd.
  7. - I/O errors for torrents no longer make btpd shut down. Instead the
  8. problematic torrent is stopped.
  9. - Added the option '--ip' to specify the ip address btpd will report
  10. to trackers.
  11. - Resume file format changed. Already added torrents will be retested once.
  12. - The torrent info (ratio etc.) are now saved regularly.
  13. - Reduced the amount of outgoing data kept in memory.
  14. btpd 0.12:
  15. ----------
  16. Misc:
  17. - btpd now starts with the same set of active torrents as it had when it was
  18. last shut down. The new '--empty-start' option disables this feature.
  19. - btpd now supports the key tracker extension.
  20. - btpd now supports the multi tracker extension.
  21. - btcli list and stat print headers for the presented data. Both commands
  22. displays more data than before.
  23. - Torrent management has changed, with changes to the add and del commands
  24. and two new commands, start and stop, as a result. Operation on torrents
  25. can now be done by number as well as torrent file.
  26. - A small delay has been added for contacting the same announce URL.
  27. - btpd sends keepalive messages.
  28. - The number of have messages sent has been reduced by not sending them to
  29. peers that already have the piece.
  30. - The structure of the torrents directory in the btpd directory has changed.
  31. It is best to remove it before running btpd 0.12.
  32. Bug fixes:
  33. - Zero sized files in a torrent were not always created.
  34. btpd 0.11:
  35. ----------
  36. Bug fixes:
  37. - A file descriptor was closed too early, which could cause btpd to exit
  38. with an error message on systems using epoll.
  39. btpd 0.10:
  40. ----------
  41. Misc:
  42. - The protection mode of the ipc socket can now be specified via the new
  43. "--ipcprot" option for btpd.
  44. Bug fixes:
  45. - The pid file is now written correctly.
  46. - btpd's "-d" option now works for relative paths too.
  47. - Add a time out for handshake completion. Prevously btpd could slowly
  48. fill with unused incoming connections.
  49. btpd 0.9:
  50. ---------
  51. Misc:
  52. - Small changes to 'btcli stat' output.
  53. Bug fixes:
  54. - Use correct value for '--prealloc' default.
  55. - Stopped torrents now show correct rates (0kB/s).
  56. - The test of content that has been modified between runs was broken.
  57. btpd 0.8:
  58. ---------
  59. Misc:
  60. - btpd now requires pthreads.
  61. - btpd keeps its logs and other information it needs in its own directory.
  62. $HOME/.btpd is the default location.
  63. - Various changes in btpd options ant btcli use. See '--help'.
  64. - The user chooses where to place content for each torrent.
  65. - Better disk IO performance.
  66. - Configureable disk preallocation to reduce file fragmentation.
  67. - The unchoke algorithm is global instead of per torrent. The number
  68. of peers to upload to is configurable.
  69. - Tracker errors are displayed in 'btcli stat' and most importantly don't
  70. make torrents unload on startup.
  71. - The rates displayed by btcli are now computed in btpd and are averaged
  72. over the last 20 seconds.
  73. - btpd now compares size and mtime of content to see if the resume file is
  74. valid.
  75. Bug fixes:
  76. - Double uninterest messages could be sent to some peers in endgame mode.
  77. - A function was called prematurely which could trigger an assert in rare
  78. cases.
  79. btpd 0.7:
  80. ---------
  81. Bug fixes:
  82. - Some communication stupidities was fixed, resulting in better download
  83. performance.
  84. btpd 0.6:
  85. ---------
  86. Misc:
  87. - Set an upper limit on how much data a peer can request at once.
  88. This protects from running out of memory because of a greedy peer.
  89. - End game is more efficient and uses much less memory.
  90. btpd 0.5:
  91. ---------
  92. Bug fixes:
  93. - The bitfield could be sent too late. This could cause the receiving
  94. peer to close the connection.
  95. btpd 0.4:
  96. ---------
  97. Misc:
  98. - The 0.1 rate limiter is back. It runs at a configurable hz now.
  99. - Added "--bw-hz" option to btpd.
  100. - Multiple have messages can be sent in place of a bitfield.
  101. - If btpd can't write to a peer for 60s, it will be disconnected.
  102. Bug fixes:
  103. - A calculation error made btpd buggy with small torrents.
  104. This caused strange crashes and many reports on bad hashes in the log.
  105. - The bitfield was sent too early. A peer could miss pieces btpd got
  106. while the peer was in handshake.
  107. - Some situations in end game or with bad hashes could cause a crash.
  108. btpd 0.3:
  109. ---------
  110. Misc:
  111. - New download strategy.
  112. - Pipe ten requests instead of five.
  113. - "-d" option added to btpd.
  114. - "--with-warn" option added to configure. The default is now
  115. to compile with warnings off.
  116. Bug fixes:
  117. - It was possible for blocks to remain marked as busy when a peer
  118. choked or was lost, causing a piece download to wait until end game.
  119. - The peer wanted level could get too high during end game.
  120. btpd 0.2:
  121. ---------
  122. Misc:
  123. - A new way to do rate limiting.
  124. - Compact mode is now used when talking to the tracker.
  125. Bug fixes:
  126. - A buffer was too small by four bytes, causing a buffer overflow
  127. on the heap in certain conditions.
  128. - An iteration over a list was unsafe and could cause a crash.
  129. - Unloading a torrent didn't kill peers in handshake for that torrent,
  130. and a crash was possible when the handshake finished.
  131. - The counter for uploaded data was updated too early.
  132. - Fixed illegal operator for test(1) in configure.