Here is the single cryptic readme for how to install and run EGADS:

The easiest method is to create an EGADS user and untar into that users
home directory.

as root:

adduser egads
passwd egads
su - egads
cd ~egads
tar -xvzf <tarfile>

Add egads user to the tty and uucp groups to give the user access to
the serial ports and /var/lock directory. Otherwise, change the ownership
or permissions of the serial port you want to access.

Install Sharc: sharc.sf.net

Look into the EGADS/bin/required file. This will tell you which perl 
modules you will need to install. Also, you will need to install the expat
library from sourceforge (expat.sf.net). This is included in many 
distributions so you may already have it installed.

Install the perl modules. If you install SOAP::Lite, it will install a
bunch of supporting modules, and will require an upgrade to 5.6.1 of perl. 
You only need to do this if you want to take advantage of the networked
features of EGADS.


Once all of this is installed, you need to configure EGADS:

edit parameters in EGADS/xml/Egads.xml
	mostly self explanatory
edit site information in EGADS/xml/MasterSites.xml
	mostly self explanatory
edit Tasks in EGADS/xml/Tasks.xml
	This is confusing as hell, but really powerful also.
	I have predefined a few tasks:
		daily (download once daily delet after 3 days)
		4hour (download every 4 hour delete after 3 days)
		hourly5 (download every hour, delete after 6 hours )
		hourly1sec (download every hour delet aftr 1 hour)
	A site can inherit these tasks by specifying the correct name
		in the inherit portion of the site line.
edit Clients in EGADS/xml/Clients.xml
	mostly self explanatory


A site will be matched to a client using the telemetry/telem_spec options
in the MasterSites.xml and Clients.xml files. 

To run the standalone version of configuring:

cd EGADS/bin
./egads_client.pl --nosoap --daemon --hub <clientname>



