clean up and name and syntax of status events

svn:r8693
This commit is contained in:
Roger Dingledine 2006-10-12 09:40:36 +00:00
parent f9325eeb29
commit c2a158f52c

View File

@ -855,14 +855,15 @@ $Id$
[First added in 0.1.2.2-alpha.] [First added in 0.1.2.2-alpha.]
4.1.10. Misc other events 4.1.10. Status events
Syntax: Syntax:
"650" SP Type SP Action SP Arguments "650" SP Type SP Action SP Arguments
Type = "MISC_CLIENT" / "MISC_SERVER" Type = "STATUS_CLIENT" / "STATUS_SERVER"
Action and Arguments (if any) are described below. 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 CIRCUIT_ESTABLISHED means that Tor is able to establish circuits
for client use. This event will only be sent if we just built a 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 that it has closed all its circuits and will establishing them
anew. This typically happens when a laptop goes to sleep and then anew. This typically happens when a laptop goes to sleep and then
wakes up again. It also happens when the system is swapping so wakes up again. It also happens when the system is swapping so
heavily that Tor is starving. The Arguments line is this case is heavily that Tor is starving. The Arguments line in this case is
a single non-negative integer representing the number of seconds "time=NUM", a non-negative integer representing the number of
Tor thinks it was unconscious for. 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: