mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2025-02-23 22:47:12 +01:00
update control spec to reflect our new SETCONF behavior
svn:r5038
This commit is contained in:
parent
ed748efd83
commit
c48cda7b02
1 changed files with 3 additions and 3 deletions
|
@ -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
|
||||
|
|
Loading…
Add table
Reference in a new issue