From: Nick Mathewson Date: Fri, 25 Mar 2005 05:49:01 +0000 (+0000) Subject: Clarify behavior of SETEVENTS: it is SET, not ADD. X-Git-Tag: tor-0.1.0.1-rc~41 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5edd94b27efd72922e1cdffe7142995b9d4438db;p=thirdparty%2Ftor.git Clarify behavior of SETEVENTS: it is SET, not ADD. svn:r3871 --- diff --git a/doc/control-spec.txt b/doc/control-spec.txt index 05b016192f..02ed15abf7 100644 --- a/doc/control-spec.txt +++ b/doc/control-spec.txt @@ -163,7 +163,8 @@ the message. Request the server to inform the client about interesting events. The body contains a list of 2-byte event codes (see "event" below). - Sending SETEVENTS with an empty body turns off all event reporting. + Any events *not* listed in the SETEVENTS body are turned off; thus, sending + SETEVENTS with an empty body turns off all event reporting. The server responds with a DONE message on success, and an ERROR message if one of the event codes isn't recognized. (On error, the list of active