Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
and not considered stable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Clean all torrents now only cleans one bucket at a time
All torrents that are being worked upon in an announce are being cleaned on demoand
torrent's peer lists now keep extra counts for seeds and peers to speed up scrape and announce
Sync has gone for now. I will think up a new way to implement. The old one was way to slow.
|
|
|
|
one or two peers, wasting 8*15 or 8*14 bytes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* implemented basic blacklisting:
** the file specified with -b <BLACKLIST> is read and added to a blacklist vector
** if an announce hits a torrent in that blacklist vector, add_peer_to_torrent fails
** sending a SIGHUP to the program forces it to reread the blacklists
** the server returns with a 500, which is not exactly nice but does the job for now
** an adaequat "failure reason:" should be delivered... TODO
|
|
|
|
torrents once every OT_POOL_TIMEOUT units.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
factor of 5
|
|
|
|
|
|
|
|
clean up.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-> this may remove peer already and must be done anyway.
|
|
|
|
|