Added an option to manually specify which address to bind to.

[distributedratelimiting.git] / drl / Manual.txt

diff --git a/drl/Manual.txt b/drl/Manual.txt
index c97c70d..0835a56 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.
 
-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
@@ -82,6 +83,10 @@ Whether or not to turn enforcement on by default at startup.  0 for off,
 anything else for on.  If unspecified, it defaults to 1.  Enforcement can be
 turned on/off at runtime with SIGUSR1.
 
+bind_addr <IP address string>
+Can be used to optionally specify which address DRL should use when binding
+its inter-limiter communication socket.
+
 netem_loss <int>
 netem_delay <int>
 netem_slice <int|ALL>
@@ -92,7 +97,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
-process SIGHUP will cause it to re-read this XML config file.  DRL supports
+process SIGUSR2 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