summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2006-10-30 02:54:44 +0000
committerRoger Dingledine <arma@torproject.org>2006-10-30 02:54:44 +0000
commitfa78bb58abe303af1250d31c4dd7cc6921eea638 (patch)
tree03aaaecf227fe264727e7e4e21cbdd6cf29f65ba
parent8a781f7f34ffa528a7f3cd2dde69e7259685c2b4 (diff)
downloadtor-fa78bb58abe303af1250d31c4dd7cc6921eea638.tar.gz
tor-fa78bb58abe303af1250d31c4dd7cc6921eea638.zip
start a tweak on the status event section, but not finished
yet. so be it. svn:r8859
-rw-r--r--doc/control-spec.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/control-spec.txt b/doc/control-spec.txt
index bafd1e6cdb..a69664b509 100644
--- a/doc/control-spec.txt
+++ b/doc/control-spec.txt
@@ -958,7 +958,7 @@ $Id$
VERBOSE_NAMES; see the explanations in the USEFEATURE section
for details.
- Actions for STATUS_GENERAL severity NOTICE events can be as follows:
+ Actions for STATUS_GENERAL events can be as follows:
CLOCK_JUMPED
"time=NUM"
@@ -968,8 +968,8 @@ $Id$
also happens when the system is swapping so heavily that Tor is
starving. The "time" argument includes the number of seconds Tor
thinks it was unconscious for.
- This status event is sent as WARN severity if Tor is acting
- as a server currently.
+ This status event is sent as NOTICE severity normally, but WARN
+ severity if Tor is acting as a server currently.
[Recommendation for controller: ignore it, since we don't really
know what the user should do anyway. Hm.]
@@ -977,7 +977,7 @@ $Id$
DIR_REACHABLE
[not implemented yet]
- Actions for STATUS_GENERAL severity WARN events can be as follows:
+ typically severity WARN events:
DANGEROUS_VERSION
"current=version"