From 5740071674f88e152ce9dd65530881874d36e037 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Wed, 14 Mar 2007 23:50:41 +0000 Subject: the spec called it a GUARDS event, but the code called it a GUARD event. standardize on GUARD, but support people asking for GUARDS too. reported by daejees. backport candidate. svn:r9817 --- doc/spec/control-spec.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/spec') diff --git a/doc/spec/control-spec.txt b/doc/spec/control-spec.txt index ffa682df3..3bf36b4d2 100644 --- a/doc/spec/control-spec.txt +++ b/doc/spec/control-spec.txt @@ -194,7 +194,7 @@ $Id$ EventCode = "CIRC" / "STREAM" / "ORCONN" / "BW" / "DEBUG" / "INFO" / "NOTICE" / "WARN" / "ERR" / "NEWDESC" / "ADDRMAP" / "AUTHDIR_NEWDESCS" / "DESCCHANGED" / "STATUS_GENERAL" / - "STATUS_CLIENT" / "STATUS_SERVER" / "GUARDS" / "NS" / "STREAM_BW" + "STATUS_CLIENT" / "STATUS_SERVER" / "GUARD" / "NS" / "STREAM_BW" Any events *not* listed in the SETEVENTS line are turned off; thus, sending SETEVENTS with an empty body turns off all event reporting. @@ -1263,7 +1263,7 @@ $Id$ 4.1.11. Our set of guard nodes has changed Syntax: - "650" SP "GUARDS" SP Type SP Name SP Status ... CRLF + "650" SP "GUARD" SP Type SP Name SP Status ... CRLF Type = "ENTRY" Name = The (possibly verbose) nickname of the guard affected. Status = "NEW" | "UP" | "DOWN" | "BAD" | "GOOD" | "DROPPED" -- cgit v1.2.3