summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2005-09-13 22:36:11 +0000
committerRoger Dingledine <arma@torproject.org>2005-09-13 22:36:11 +0000
commitc48cda7b02d68938e15fd32c14d8ce42e928607a (patch)
treeeb76104e8ebcac9b525d47b1dd6bd6036b9a87d0
parented748efd83b6455dadedf9f7aef87872b821a3be (diff)
downloadtor-c48cda7b02d68938e15fd32c14d8ce42e928607a.tar.gz
tor-c48cda7b02d68938e15fd32c14d8ce42e928607a.zip
update control spec to reflect our new SETCONF behavior
svn:r5038
-rw-r--r--doc/control-spec.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/control-spec.txt b/doc/control-spec.txt
index 84370ade76..cf653fb432 100644
--- a/doc/control-spec.txt
+++ b/doc/control-spec.txt
@@ -110,9 +110,9 @@ $Id$
Tor behaves as though it had just read each of the key-value pairs
from its configuration file. Keywords with no corresponding values have
- their configuration values reset to their defaults. SETCONF is
- all-or-nothing: if there is an error in any of the configuration settings,
- Tor sets none of them.
+ their configuration values reset to 0 or "" (use RESETCONF if you want
+ to set it back to its default). SETCONF is all-or-nothing: if there
+ is an error in any of the configuration settings, Tor sets none of them.
Tor responds with a "250 configuration values set" reply on success.
Tor responds with a "513 syntax error in configuration values" reply on