Changes between Version 1 and Version 2 of GIMSDocumentation

Timestamp:

08/05/10 15:53:14 (14 years ago)

Author:

jsommers@colgate.edu

Comment:

--

GIMSDocumentation

@@ -9 +9 @@
 
 '''capture-daemon'''
-
 ----
 
@@ -38 +37 @@
 
 The only software dependency for the basic functionality of
-capture-daemon is a working libpcap library.
+capture-daemon is a working libpcap library.  
 
 For flow aggregation in IPFIX records, libyaf and libfixbuf are
@@ -47 +46 @@
 better.  See the yaf/fixbuf documentation for more details.
 
-From inside the capture-daemon subdirectory, configure and make, then
-sudo make install.  (Make install just changes the capture-daemon
+From inside the capture-daemon subdirectory, do a "./configure"
+then a make, then sudo make install.  (Make install just changes the capture-daemon
 binary to be suid root so that it can have permissions to set a net
 device in promiscuous mode.  Alternatively, run capd_proxy.py as root.)
@@ -54 +53 @@
 
 '''capd_proxy.py'''
-
 ----
 
-Requires python 2.6.
+Requires python 2.6 or better (but not 3.x)
 
 The capd_proxy handles all XML/RPC functions for configuring,
@@ -72 +70 @@
 
 From the capture daemon proxy, a separate process is started up to
-handle each storage type (s3, ssh, and local storage).  This storage
+handle storage uploads (s3, ssh, and local storage).  This storage
 process handles checking for new files that can be uploaded, and also
 annotates the existing metadata for raw capture files prior to upload.
@@ -79 +77 @@
 transfer.  (Note that some work is yet to be done on ensuring the
 propagation of errors from storage uploads to the UI (and
-experimenters).)  Storage functionality is almost entirely housed in
+experimenters).)  Storage functionality is entirely housed in
 the capd_storage.py module.