aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2005-11-17 22:01:24 +0000
committerRoger Dingledine <arma@torproject.org>2005-11-17 22:01:24 +0000
commit396577d17e3124e30b39d84de883165d07582c8a (patch)
treefc4251ce19b84f8f270531447e1ca5ead712a40b /doc
parent7dbf2511c39e47db609c77e255dc1a186b8e1ff1 (diff)
downloadtor-396577d17e3124e30b39d84de883165d07582c8a.tar.gz
tor-396577d17e3124e30b39d84de883165d07582c8a.zip
what to do on a failed setconf was a bit unspecified
svn:r5413
Diffstat (limited to 'doc')
-rw-r--r--doc/control-spec.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/control-spec.txt b/doc/control-spec.txt
index ed1813abcd..b38d1b57ef 100644
--- a/doc/control-spec.txt
+++ b/doc/control-spec.txt
@@ -115,9 +115,10 @@ $Id$
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
- syntax error, or a "553 impossible configuration setting" reply on a
- semantic error.
+ If some of the listed keywords can't be found, Tor replies with a
+ "552 Unrecognized option" message. Otherwise, Tor responds with a
+ "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
@@ -151,7 +152,7 @@ $Id$
250 keyword
If some of the listed keywords can't be found, Tor replies with a
- "552 unknown configuration keyword" message.
+ "552 unknown configuration keyword" message.
If an option appears multiple times in the configuration, all of its
key-value pairs are returned in order.