aboutsummaryrefslogtreecommitdiff
path: root/doc/HACKING
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2004-03-30 03:20:38 +0000
committerRoger Dingledine <arma@torproject.org>2004-03-30 03:20:38 +0000
commit414dff42c5f5046201bd560f9ecfaa2b670e4016 (patch)
tree71bfae5ca1b6817d598270879956b77b0b250572 /doc/HACKING
parent524312494b5c5b015dd7f0db350c959afdefcf9a (diff)
downloadtor-414dff42c5f5046201bd560f9ecfaa2b670e4016.tar
tor-414dff42c5f5046201bd560f9ecfaa2b670e4016.tar.gz
update hacking to mention loglevel notice
svn:r1385
Diffstat (limited to 'doc/HACKING')
-rw-r--r--doc/HACKING5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/HACKING b/doc/HACKING
index 046521b3e..3722aa5e8 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -1,4 +1,4 @@
- Guide to Hacking Tor
+ Guide to Hacking Tor
(As of 8 October 2003, this was all accurate. If you're reading this in
the distant future, stuff may have changed.)
@@ -398,8 +398,9 @@ the distant future, stuff may have changed.)
bad thing is either a bug in the code, an attack or buggy
protocol/implementation of the remote peer, etc. The operator should
examine the bad thing and try to correct it.
+ NOTICE if it's something the operator will want to know about.
(No error or warning messages should be expected during normal OR or OP
- operation. I expect most people to run on -l warn eventually. If a
+ operation. I expect most people to run on -l notice eventually. If a
library function is currently called such that failure always means
ERR, then the library function should log WARN and let the caller
log ERR.)