Contents of the directory
--------------------------
1. filebench: This directory contains the patch for CentOS Linux and to 
	enable energy readings from the wattsup meter.

2. auto-pilot: This directory contains the auto-pilot scripts used for 
	benchmarking and running the four filebench workloads:
	webserver, varmail, oltp and file server.

	The details about auto-pilot and how to use it is given at:
	http://www.fsl.cs.sunysb.edu/project-autopilot.html.  
	NOTE: Please read the documentation on auto-pilot before 
	running these tests.

	The auto-pilot scripts are as follows:
	a. *.ap file: There are 31 such files, each file representing 
		file system type, format and mount option for all the 
		four workloads.  

	b. fs-setup.sh: This is the pre-test script executed by all 
		the .ap files. It formats and mounts the file system.

	c. fs-cleanup.sh: This is the post-test script which unmounts
		the file system.

	d. filebench.sh: Shell script invoked from .ap file to actually
		run the filebench test.

	e. fsbench_common.inc: This file contains the auto-pilot 
		configurations, result and log directories. Please 
		refer the example and comments in this file.

	f. filebench: Auto-pilot hook for fsgreen_bench. This file should
		be copied to the /usr/local/share/auto-pilot/commonsettings.d/

	g. getstats: To extract the output information from the .res files.
		
Installation Steps
-------------------
1. Download and install auto-pilot-2.4 from www.fsl.cs.sunysb.edu/project-autopilot.html
2. Download filebench-1.4.8 and apply the patch provided in src/filebench/.
   Follow the instructions in the filebench-1.4.8 of how to compile 
   and install the software.  

Steps to run the benchmark
---------------------------
1. Update the environment variables in fsbench_common.inc (i.e.,
   test directory, partition, etc.).
2. Run the following command from the src/auto-pilot directory:
	auto-pilot <filename.ap>, where
	filename.ap is any of the ".ap" files in this directory.

3. To extract the results from the test run, execute the following 
   command:
	./getstats <file.res>, where
	file.res is the result file generated from the test run. 

