commit db004cb32f97bd8a72035f270948ff2e9b430899 Author: Damian Johnson atagar@torproject.org Date: Sat May 21 17:59:06 2016 -0700
Sort events alphabetically
With the exception of the runlevels sorting the events to make them easier to find. --- stem/settings.cfg | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/stem/settings.cfg b/stem/settings.cfg index 48a1a41..aafeafd 100644 --- a/stem/settings.cfg +++ b/stem/settings.cfg @@ -370,24 +370,25 @@ event.description.info Logging at the info runlevel. This is low level informati event.description.notice Logging at the notice runlevel. This runlevel and above are shown to users by default, and includes general information the user should be aware of. event.description.warn Logging at the warning runlevel. These are problems the user should be aware of. event.description.err Logging at the error runlevel. These are critical issues that may prevent tor from working properly. -event.description.circ Indicates that a circuit we've established through the tor network has been created, changed, or closed. -event.description.circ_minor Minor changes to our circuits, such as reuse of existing circuits for a different purpose. -event.description.stream Communication over a circuit we've established. For instance, Firefox making a connection through tor. -event.description.orconn Change in our connections as a relay. -event.description.bw Event emitted every second with the bytes sent and received by tor. -event.description.newdesc Indicates that a new descriptor is available. + event.description.addrmap New address mapping for our DNS cache. event.description.authdir_newdescs Indicates we just received a new descriptor. This is only used by directory authorities. +event.description.buildtimeout_set Indicates the timeout value for a circuit has changed. +event.description.bw Event emitted every second with the bytes sent and received by tor. +event.description.circ Indicates that a circuit we've established through the tor network has been created, changed, or closed. +event.description.circ_minor Minor changes to our circuits, such as reuse of existing circuits for a different purpose. +event.description.clients_seen Periodic summary of the countries we've seen users connect from. This is only used by bridge relays. +event.description.conf_changed Indicates that our torrc configuration has changed. This could be in response to a SETCONF or RELOAD signal. event.description.descchanged Indicates that our descriptor has changed. +event.description.guard Indicates that the set of relays we use for our initial connection into the tor network (guards) have changed. +event.description.newconsensus Received a new hourly consensus of relays in the tor network. +event.description.newdesc Indicates that a new descriptor is available. event.description.ns Consensus information for an individual relay has changed. This could be due to receiving a new consensus or tor locally decides a relay is up or down. -event.description.status_general Notification of a change in tor's state. +event.description.orconn Change in our connections as a relay. +event.description.signal Indicates that tor has received and acted upon a signal being sent to its process. event.description.status_client Notification of a change in tor's state as a client (ie user). +event.description.status_general Notification of a change in tor's state. event.description.status_server Notification of a change in tor's state as a relay. -event.description.guard Indicates that the set of relays we use for our initial connection into the tor network (guards) have changed. +event.description.stream Communication over a circuit we've established. For instance, Firefox making a connection through tor. event.description.stream_bw Event emitted every second with the bytes sent and received for a specific stream. -event.description.clients_seen Periodic summary of the countries we've seen users connect from. This is only used by bridge relays. -event.description.newconsensus Received a new hourly consensus of relays in the tor network. -event.description.buildtimeout_set Indicates the timeout value for a circuit has changed. -event.description.signal Indicates that tor has received and acted upon a signal being sent to its process. -event.description.conf_changed Indicates that our torrc configuration has changed. This could be in response to a SETCONF or RELOAD signal.