nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-24 04:13:28 +01:00
Code Issues Packages Projects Releases Wiki Activity

update hacking to mention loglevel notice

Browse Source 
svn:r1385
This commit is contained in:
Roger Dingledine 2004-03-30 03:20:38 +00:00
parent 524312494b
commit 414dff42c5
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/HACKING
View File

@ -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 (As of 8 October 2003, this was all accurate. If you're reading this in
the distant future, stuff may have changed.) 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 bad thing is either a bug in the code, an attack or buggy
protocol/implementation of the remote peer, etc. The operator should protocol/implementation of the remote peer, etc. The operator should
examine the bad thing and try to correct it. 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 (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 library function is currently called such that failure always means
ERR, then the library function should log WARN and let the caller ERR, then the library function should log WARN and let the caller
log ERR.) log ERR.)