[or-cvs] OR_CONN_EVENT_NEW: we should probably handle that , should ...
Nick Mathewson
nickm at seul.org
Tue Jul 11 03:33:19 UTC 2006
Update of /home/or/cvsroot/tor/src/or
In directory moria:/tmp/cvs-serv21667/src/or
Modified Files:
control.c
Log Message:
OR_CONN_EVENT_NEW: we should probably handle that , should we not? Especially since 23:26 < phobos> nickm: grep -c "Unrecognized status code 4" tor.log
Index: control.c
===================================================================
RCS file: /home/or/cvsroot/tor/src/or/control.c,v
retrieving revision 1.195
retrieving revision 1.196
diff -u -p -d -r1.195 -r1.196
--- control.c 22 Jun 2006 07:01:54 -0000 1.195
+++ control.c 11 Jul 2006 03:33:16 -0000 1.196
@@ -2735,6 +2735,7 @@ control_event_or_conn_status(connection_
case OR_CONN_EVENT_CONNECTED: status = "CONNECTED"; break;
case OR_CONN_EVENT_FAILED: status = "FAILED"; break;
case OR_CONN_EVENT_CLOSED: status = "CLOSED"; break;
+ case OR_CONN_EVENT_NEW: status = "NEW"; break;
default:
log_warn(LD_BUG, "Unrecognized status code %d", (int)tp);
return 0;
More information about the tor-commits
mailing list