[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r8859: start a tweak on the status event section, but not finished (tor/trunk/doc)
- To: or-cvs@xxxxxxxxxxxxx
- Subject: [or-cvs] r8859: start a tweak on the status event section, but not finished (tor/trunk/doc)
- From: arma@xxxxxxxx
- Date: Sun, 29 Oct 2006 21:54:44 -0500 (EST)
- Delivered-to: archiver@seul.org
- Delivered-to: or-cvs-outgoing@seul.org
- Delivered-to: or-cvs@seul.org
- Delivery-date: Sun, 29 Oct 2006 21:54:51 -0500
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-cvs@xxxxxxxxxxxxx
Author: arma
Date: 2006-10-29 21:54:44 -0500 (Sun, 29 Oct 2006)
New Revision: 8859
Modified:
tor/trunk/doc/control-spec.txt
Log:
start a tweak on the status event section, but not finished
yet. so be it.
Modified: tor/trunk/doc/control-spec.txt
===================================================================
--- tor/trunk/doc/control-spec.txt 2006-10-29 21:53:24 UTC (rev 8858)
+++ tor/trunk/doc/control-spec.txt 2006-10-30 02:54:44 UTC (rev 8859)
@@ -958,7 +958,7 @@
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 @@
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 @@
DIR_REACHABLE
[not implemented yet]
- Actions for STATUS_GENERAL severity WARN events can be as follows:
+ typically severity WARN events:
DANGEROUS_VERSION
"current=version"