From c48cda7b02d68938e15fd32c14d8ce42e928607a Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Tue, 13 Sep 2005 22:36:11 +0000 Subject: [PATCH] update control spec to reflect our new SETCONF behavior svn:r5038 --- doc/control-spec.txt | 6 +++--- 1 file 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