Changeset 108 for trunk

Timestamp:

04/20/09 15:14:26 (14 years ago)

Author:

andreu

Message:

new configuration files (*_MS.txt) for multi-sampling mode
README update

Location:

trunk

Files:

• README (modified) (4 diffs)
• conf/AS_MS.txt (added)
• conf/IPv4_Subnet_Aggregation_based_on_SNMP_index_MS.txt (added)

trunk/README

@@ -46 +46 @@
         ./renetcol ... : launch the collector (you must be root)
         ./renetcolSender ... : to use remote client
-        ./renetcolMsgCtl ... : to kill the IPC message queue if you kill renetcol  
+        ./renetcolMsgCtl ... : to kill the IPC message queue if you kill renetcol 
 
 We recommand to use the script *check.sh* (in tool/) to launch renetcol. 
-This script required in parameters the path to renetcol and you must edit the file.
+This script required in parameters the path to renetcol.
 We can also put the script in your root crontab to verify the collector state, 
 for exemple:
@@ -55 +55 @@
  /bin/sh <path>/renetcol-0.0.14beta/tool/check.sh <path>/renetcol-0.0.14beta/
 
- -------------------
-| Commands exemples |
- -------------------
+ --------------------------
+| Others Commands exemples |
+ --------------------------
 
 colnet:/tmp/renetcol_user/src# killall renetcol
@@ -88 +88 @@
     *REQUIRED* In this release the client tool host MUST be have a
  reverse DNS for his name. If not the collector will not be able to 
-communicate with the client. Explication: the rules are registered on the 
-collector in the conf file (rules.txt) in such way:
+communicate with the client. Explication: filters are registered on the 
+collector in a file (rules.txt) in such way:
         N 53.renater.fr
         O socket 53.renater.fr 2222
@@ -99 +99 @@
 
 The client tool can be used on the collector box or in remote mode. You can 
-used few clients instantiations (on differents remotes PCs).
+used few clients instantiations (on differents remotes computers).