From 86eb8db0f052e6eded8abc4da87a1cb2e82c5f2d Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Mon, 22 Jul 2002 04:07:34 +0000 Subject: Updated HACKING and README docs HACKING now explains bandwidth throttling, congestion control, and router twins. Read it and see if it makes sense. svn:r68 --- README | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'README') diff --git a/README b/README index 2c0a942fb..842dba4d1 100644 --- a/README +++ b/README @@ -13,7 +13,8 @@ If you got the source from cvs: If you got the source from a tarball: - Run ./configure, make, make install as usual. + Run ./configure and make as usual. There isn't much point in + 'make install' yet. If this doesn't work for you: @@ -23,7 +24,6 @@ If this doesn't work for you: we'll see what we can do. Once you've got it compiled: - (these notes assume you started with source from cvs) It's a bit hard to figure out what to do with the binaries. If you want to set up your own test network, go into src/config/ and look @@ -54,8 +54,9 @@ Once you've got it compiled: then ^z the wget a little bit in. The onion routers will continue talking for a while, queueing around 500k in the kernel-level buffers. When the kernel buffers are full, and the outbuf for the AP connection - also fills, the internal congestion control will kick in and the - exit connection will stop reading from the webserver. The circuit - will wait until you fg the wget -- and other circuits will work just - fine throughout. + also fills, the internal congestion control will kick in and the exit + connection will stop reading from the webserver. The circuit will + wait until you fg the wget -- and other circuits will work just fine + throughout. Then try ^z'ing the onion routers, and watch how well it + recovers. Then try ^z'ing several of them at once. :) -- cgit v1.2.3