git://git.onelab.eu
/
distributedratelimiting.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
d15c193
)
Signal documentation
author
Kevin Webb
<kcwebb@ucsd.edu>
Wed, 27 Jan 2010 22:10:40 +0000
(22:10 +0000)
committer
Kevin Webb
<kcwebb@ucsd.edu>
Wed, 27 Jan 2010 22:10:40 +0000
(22:10 +0000)
drl/Manual.txt
patch
|
blob
|
history
diff --git
a/drl/Manual.txt
b/drl/Manual.txt
index
c97c70d
..
bf5fed8
100644
(file)
--- a/
drl/Manual.txt
+++ b/
drl/Manual.txt
@@
-58,7
+58,8
@@
responsiveness but incur higher overhead. NOTE: this is in milliseconds.
Generally, 500ms works well for FPS. GRD needs a faster interval, generally
50-100ms.
Generally, 500ms works well for FPS. GRD needs a faster interval, generally
50-100ms.
-drl_logfile specifies where the drl logfile should be written.
+drl_logfile specifies where the drl logfile should be written. DRL will
+reopen the logfile when it receives SIGHUP.
drl_loglevel specifies the verbosity of logging. 1 - Debug, 2 - Info, 3 -
Critical. You probably know if you want Debug... Info logs detailed traffic
drl_loglevel specifies the verbosity of logging. 1 - Debug, 2 - Info, 3 -
Critical. You probably know if you want Debug... Info logs detailed traffic
@@
-92,7
+93,7
@@
experimentation.
The second file (whose location is determined by drl_configfile) is an XML
file containing a series of DRL identity specifications. Sending the ulogd
The second file (whose location is determined by drl_configfile) is an XML
file containing a series of DRL identity specifications. Sending the ulogd
-process SIG
HUP
will cause it to re-read this XML config file. DRL supports
+process SIG
USR2
will cause it to re-read this XML config file. DRL supports
two types of identities. 1) machine identities: A machine identity is
responsible for limiting all traffic that leaves a machine, regardless of the
traffic's sliver of origin. 2) set identities: A set identity is responsible
two types of identities. 1) machine identities: A machine identity is
responsible for limiting all traffic that leaves a machine, regardless of the
traffic's sliver of origin. 2) set identities: A set identity is responsible