[tor-commits] [tor/master] Update manpage.

[nickm at torproject.org]

commit 43a00877cf01888229d5d34085a2b75748848af1
Author: Mike Perry <mikeperry-git at fscked.org>
Date:   Mon Dec 10 00:13:55 2012 -0800

    Update manpage.
---
 doc/tor.1.txt |   12 +++++++++---
 1 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index 734bc64..7ceefb6 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -1183,12 +1183,18 @@ The following options are useful only for clients (that is, if
 
 **PathBiasMultFactor** __NUM__ +
 
-**PathBiasScaleFactor** __NUM__::
+**PathBiasScaleFactor** __NUM__ +
+
+**PathBiasUseCloseCounts** __NUM__::
     These options override the default behavior of Tor's (**currently
     experimental**) path bias detection algorithm. To try to find broken or
     misbehaving guard nodes, Tor looks for nodes where more than a certain
-    fraction of circuits through that node fail after the first hop.  The
-    PathBiasCircThreshold option controls how many circuits we need to build
+    fraction of circuits through that guard fail to get built. If
+    PathBiasUseCloseCounts is set to 1 (the default), usage-based accounting is
+    performed, and circuits that fail to carry streams are also counted as
+    failures. +
+ +
+    The PathBiasCircThreshold option controls how many circuits we need to build
     through a guard before we make these checks.  The PathBiasNoticeRate,
     PathBiasWarnRate and PathBiasExtremeRate options control what fraction of
     circuits must succeed through a guard so we won't write log messages.