From c2a158f52c0509a0c42a49ab83b108b0f8eda635 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Thu, 12 Oct 2006 09:40:36 +0000 Subject: [PATCH] clean up and name and syntax of status events svn:r8693 --- doc/control-spec.txt | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/doc/control-spec.txt b/doc/control-spec.txt index a10774ae64..b26679f4cb 100644 --- a/doc/control-spec.txt +++ b/doc/control-spec.txt @@ -855,14 +855,15 @@ $Id$ [First added in 0.1.2.2-alpha.] -4.1.10. Misc other events +4.1.10. Status events Syntax: "650" SP Type SP Action SP Arguments - Type = "MISC_CLIENT" / "MISC_SERVER" - Action and Arguments (if any) are described below. + Type = "STATUS_CLIENT" / "STATUS_SERVER" + Action is a string, and Arguments is a series of key=value + pairs; more details below. - Actions for MISC_CLIENT events can be as follows: + Actions for STATUS_CLIENT events can be as follows: CIRCUIT_ESTABLISHED means that Tor is able to establish circuits for client use. This event will only be sent if we just built a @@ -873,11 +874,12 @@ $Id$ that it has closed all its circuits and will establishing them anew. This typically happens when a laptop goes to sleep and then wakes up again. It also happens when the system is swapping so - heavily that Tor is starving. The Arguments line is this case is - a single non-negative integer representing the number of seconds - Tor thinks it was unconscious for. + heavily that Tor is starving. The Arguments line in this case is + "time=NUM", a non-negative integer representing the number of + seconds Tor thinks it was unconscious for. - Actions for MISC_SERVER events can be as follows: + + Actions for STATUS_SERVER events can be as follows: