| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
|
|
|
| |
clean up on exit for unix domain socket transport.
|
| |
|
| |
|
| |
|
|
|
|
| |
from topology file
|
| |
|
|
|
|
| |
GNUNET_CORE_iterate_peers call to work properly.
|
|
|
|
| |
white space changes)
|
|
|
|
| |
code is still buggy
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
connected (or possibly timed out connecting)
|
|
|
|
| |
debugging)
|
|
|
|
| |
peers to topology
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
maximum number of peers testing
|
| |
|
|
|
|
| |
others
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
connections (not sure where all that cpu is going)
|
| |
|
| |
|
| |
|
|
|
|
| |
testcase/user can decide how long to wait as opposed to arbitrary wait counts
|
| |
|
|
|
|
| |
better topology creation and more options therein, changes to order of starting peers, connecting peers... new order is hostkey create, topology create, blacklist create, start peers, connect peers
|
| |
|
| |
|
| |
|
| |
|
| |
|