[tor-commits] [torspec/master] neena got (reasonably) confused by context-sensitive config options

[arma@xxxxxxxxxxxxxx]

commit 22959c4230a53a1f3b22418fc8b46c0abd40ad7a
Author: Roger Dingledine <arma@xxxxxxxxxxxxxx>
Date:   Sat Jun 23 03:46:32 2012 -0400

    neena got (reasonably) confused by context-sensitive config options
---
 control-spec.txt |   14 ++++++++------
 1 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/control-spec.txt b/control-spec.txt
index 7e7e37e..40c88e8 100644
--- a/control-spec.txt
+++ b/control-spec.txt
@@ -223,12 +223,14 @@
   "513 syntax error in configuration values" reply on syntax error, or a
   "553 impossible configuration setting" reply on a semantic error.
 
-  When a configuration option takes multiple values, or when multiple
-  configuration keys form a context-sensitive group (see GETCONF below), then
-  setting _any_ of the options in a SETCONF command is taken to reset all of
-  the others.  For example, if two ORBindAddress values are configured, and a
-  SETCONF command arrives containing a single ORBindAddress value, the new
-  command's value replaces the two old values.
+  Some configuration options (e.g. "Bridge") take multiple values. Also,
+  some configuration keys (e.g. for hidden services and for entry
+  guard lists) form a context-sensitive group where order matters (see
+  GETCONF below). In these cases, setting _any_ of the options in a
+  SETCONF command is taken to reset all of the others. For example,
+  if two ORBindAddress values are configured, and a SETCONF command
+  arrives containing a single ORBindAddress value, the new command's
+  value replaces the two old values.
 
   Sometimes it is not possible to change configuration options solely by
   issuing a series of SETCONF commands, because the value of one of the

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits