From 266bcb55dbeb328bc583f3b712e7ab90d7ff004e Mon Sep 17 00:00:00 2001 From: Kevin Webb Date: Wed, 27 Jan 2010 22:10:40 +0000 Subject: [PATCH] Signal documentation --- drl/Manual.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drl/Manual.txt b/drl/Manual.txt index c97c70d..bf5fed8 100644 --- 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 @@ -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 -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 -- 2.43.0