
Reportsock!
=-=-=-=-=-=
This is ALL under the GPL license. However, I do ask if you use this to 
at least keep my name (Greg Webster) and the company I work for while 
I created this (In-Touch Software, www.intouch.ca), listed somewhere. 
Thanks!

Installation 2003/04/24
=-=-=-=-=-=-=-=-=-=-=-=

1. Create a user called 'reportsock'
2. Edit /etc/password and change reportsock's shell to something a 
little safer, like /bin/false
3. Place reportsock.conf, reportsock.pl, reporttotmp.pl in reportsock's 
home directory
4. Verify the following permissions:
	- chmod 755 reportsock.pl
	- chmod +s reportsock.pl
	- chmod 644 reportsock.conf
	- chmod 755 reporttotmp.pl
5. Verify the following ownership:
	- chown reportsock:reportsock report*.*
6. Set up a cron job for reporttotmp.pl:
	- */5 * * * * /home/reportsock/reporttotmp.pl > /dev/null 2>&1
7. Edit reportsock.conf to match your existing system
8. Edit reportsock.pl and change the LocalAddr to match your hostname 
or IP address
9. Run reportsock.pl, you should see something like:
	- Starting: <URL:"http://localhost:44000/">
10. Verify the port has been opened by running:
	- nmap -sT -p 44000 localhost
11. Set up your system-checker for the following strings:
	BAD (something is wrong, send out an alert)
	OK Load OK CPU OK Swap OK (everything is good)

Known Bugs!
=-=-=-=-=-=
- If you request the info too often, the port locks up for a while. 
There are no child processes currently enabled to solve this.
- It's not handling multiple disk partitions properly; works great if 
all you have is hda1.
- Not everyone's 'top' command is identical. Probably the solution to 
this is to get the information for reporttotmp.pl somewhere in /proc
