Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 195 lines (159 sloc) 6.333 kb
b132820 @rmn64k Text updates for btpd 0.15.
rmn64k authored
1 btpd 0.15:
2 ----------
3
4 Bug fixes:
5 - The event loop could busy loop for up to a millisecond sometimes.
6 - On some platforms btpd couldn't initiate connections to other peers.
7 - The timer code was broken on MacOS X.
8
13f376e @rmn64k Text updates for btpd 0.14.
rmn64k authored
9 btpd 0.14:
10 ----------
11
12 Misc:
13 - IPv6 support.
14 - Bans peers with bad data.
15 - Better tracker compatability and more reliable tracker communication.
16 - Show tracker counts in btcli stat.
17 - Compiles on Solaris 10.
18 - Btpd will now signal startup failures via the process exit value and
19 print the failure reason to stdout.
20 - Better shutdown and torrent stop behaviour.
21 - Needs pthreads again.
22 - Removed libevent in favour of own event loop code.
23
24 Bug fixes:
25 - An integer array was misaligned, which could cause crashes on systems
26 with alignment requirements. E.g., on XScale arm.
27 - An error in the torrent parsing code could cause crashes.
28 - The '--topdir' option to btcli add didn't work properly for single file
29 torrents.
30 - The system name lookup scheme is now used. In btpd 0.13 only dns lookups
31 were performed.
32
bac7eb9 @rmn64k Changes for 0.13.
rmn64k authored
33 btpd 0.13:
34 ----------
35
36 Misc:
37 - cURL is no longer required. btpd now uses its own http client.
e8a5b6c @rmn64k Added some more info to CHANGES and version information to README.
rmn64k authored
38 - btpd doesn't use threads anymore, so pthreads are not required.
39 - Needed parts of libevent are now included in btpd.
bac7eb9 @rmn64k Changes for 0.13.
rmn64k authored
40 - I/O errors for torrents no longer make btpd shut down. Instead the
41 problematic torrent is stopped.
42 - Added the option '--ip' to specify the ip address btpd will report
43 to trackers.
44 - Resume file format changed. Already added torrents will be retested once.
45 - The torrent info (ratio etc.) are now saved regularly.
e8a5b6c @rmn64k Added some more info to CHANGES and version information to README.
rmn64k authored
46 - Reduced the amount of outgoing data kept in memory.
bac7eb9 @rmn64k Changes for 0.13.
rmn64k authored
47
51e084f @rmn64k Document changes for 0.12.
rmn64k authored
48 btpd 0.12:
49 ----------
50
51 Misc:
52 - btpd now starts with the same set of active torrents as it had when it was
53 last shut down. The new '--empty-start' option disables this feature.
54 - btpd now supports the key tracker extension.
55 - btpd now supports the multi tracker extension.
56 - btcli list and stat print headers for the presented data. Both commands
57 displays more data than before.
58 - Torrent management has changed, with changes to the add and del commands
59 and two new commands, start and stop, as a result. Operation on torrents
60 can now be done by number as well as torrent file.
61 - A small delay has been added for contacting the same announce URL.
62 - btpd sends keepalive messages.
63 - The number of have messages sent has been reduced by not sending them to
64 peers that already have the piece.
65 - The structure of the torrents directory in the btpd directory has changed.
66 It is best to remove it before running btpd 0.12.
67
68 Bug fixes:
69 - Zero sized files in a torrent were not always created.
70
eb1581a @rmn64k Change version to 0.11 and document the changes.
rmn64k authored
71 btpd 0.11:
72 ----------
73
74 Bug fixes:
75 - A file descriptor was closed too early, which could cause btpd to exit
76 with an error message on systems using epoll.
77
45ceb46 @rmn64k Change version to 0.10 and document the changes.
rmn64k authored
78 btpd 0.10:
79 ----------
80
81 Misc:
82 - The protection mode of the ipc socket can now be specified via the new
83 "--ipcprot" option for btpd.
84
85 Bug fixes:
86 - The pid file is now written correctly.
87 - btpd's "-d" option now works for relative paths too.
88 - Add a time out for handshake completion. Prevously btpd could slowly
89 fill with unused incoming connections.
90
3c5beea @rmn64k Changes for 0.9.
rmn64k authored
91 btpd 0.9:
92 ---------
93
94 Misc:
95 - Small changes to 'btcli stat' output.
96
97 Bug fixes:
98 - Use correct value for '--prealloc' default.
99 - Stopped torrents now show correct rates (0kB/s).
100 - The test of content that has been modified between runs was broken.
101
2d696ed @rmn64k Changes for 0.8.
rmn64k authored
102 btpd 0.8:
103 ---------
104
105 Misc:
106 - btpd now requires pthreads.
107 - btpd keeps its logs and other information it needs in its own directory.
108 $HOME/.btpd is the default location.
109 - Various changes in btpd options ant btcli use. See '--help'.
110 - The user chooses where to place content for each torrent.
111 - Better disk IO performance.
112 - Configureable disk preallocation to reduce file fragmentation.
113 - The unchoke algorithm is global instead of per torrent. The number
114 of peers to upload to is configurable.
115 - Tracker errors are displayed in 'btcli stat' and most importantly don't
116 make torrents unload on startup.
117 - The rates displayed by btcli are now computed in btpd and are averaged
118 over the last 20 seconds.
119 - btpd now compares size and mtime of content to see if the resume file is
120 valid.
121
122 Bug fixes:
123 - Double uninterest messages could be sent to some peers in endgame mode.
124 - A function was called prematurely which could trigger an assert in rare
125 cases.
126
127 btpd 0.7:
8033ec3 @rmn64k Set version to 0.7. Update CHANGES.
rmn64k authored
128 ---------
129
130 Bug fixes:
131 - Some communication stupidities was fixed, resulting in better download
132 performance.
133
2d696ed @rmn64k Changes for 0.8.
rmn64k authored
134 btpd 0.6:
777c7e6 @rmn64k Changes for 0.6.
rmn64k authored
135 ---------
136
137 Misc:
138 - Set an upper limit on how much data a peer can request at once.
139 This protects from running out of memory because of a greedy peer.
140 - End game is more efficient and uses much less memory.
141
2d696ed @rmn64k Changes for 0.8.
rmn64k authored
142 btpd 0.5:
e485377 @rmn64k The fix for bitfield in r59 wasn't quite correct. Instead of
rmn64k authored
143 ---------
144
145 Bug fixes:
146 - The bitfield could be sent too late. This could cause the receiving
147 peer to close the connection.
148
2d696ed @rmn64k Changes for 0.8.
rmn64k authored
149 btpd 0.4:
0537ec3 @rmn64k Add items for 0.4.
rmn64k authored
150 ---------
151
152 Misc:
153 - The 0.1 rate limiter is back. It runs at a configurable hz now.
154 - Added "--bw-hz" option to btpd.
155 - Multiple have messages can be sent in place of a bitfield.
156 - If btpd can't write to a peer for 60s, it will be disconnected.
157
158 Bug fixes:
159 - A calculation error made btpd buggy with small torrents.
160 This caused strange crashes and many reports on bad hashes in the log.
161 - The bitfield was sent too early. A peer could miss pieces btpd got
162 while the peer was in handshake.
163 - Some situations in end game or with bad hashes could cause a crash.
164
2d696ed @rmn64k Changes for 0.8.
rmn64k authored
165 btpd 0.3:
7ced6ad @rmn64k Prepare for release 0.3.
rmn64k authored
166 ---------
167
168 Misc:
169 - New download strategy.
b7e1e47 @rmn64k Add item for 0.3.
rmn64k authored
170 - Pipe ten requests instead of five.
7ced6ad @rmn64k Prepare for release 0.3.
rmn64k authored
171 - "-d" option added to btpd.
172 - "--with-warn" option added to configure. The default is now
173 to compile with warnings off.
174
175 Bug fixes:
176 - It was possible for blocks to remain marked as busy when a peer
177 choked or was lost, causing a piece download to wait until end game.
178 - The peer wanted level could get too high during end game.
179
4aaf966 @rmn64k Add CHANGES. A file describing changes between versions of btpd.
rmn64k authored
180 btpd 0.2:
181 ---------
182
183 Misc:
184 - A new way to do rate limiting.
185 - Compact mode is now used when talking to the tracker.
186
187 Bug fixes:
188 - A buffer was too small by four bytes, causing a buffer overflow
189 on the heap in certain conditions.
190 - An iteration over a list was unsafe and could cause a crash.
191 - Unloading a torrent didn't kill peers in handshake for that torrent,
192 and a crash was possible when the handshake finished.
193 - The counter for uploaded data was updated too early.
194 - Fixed illegal operator for test(1) in configure.
Something went wrong with that request. Please try again.