Read Me

General Information:
	Developed in Python 2.6.4 by William Huba, November 2009
	Buzhug database (http://buzhug.sourceforge.net/)
		There is a limit of (2^31)-1 bytes per field (about 2.2 GB), no limit per record. A string field takes 2+len(string) bytes to store on a disk. The longest field for a syslog packet is the message at about 30-50 characters. At an average of 42 bytes per message, this means a maximum of about 51 million strings could be stored in the message field before the database reaches capacity.
	Currently no installer, but location must be set in index.py
	Listens on port 514
	Database automatically cleansed weekly
		Day and hour are configurable, see the GUI section.
		All messages written to the Logs folder with a name of YearMonthDay.log and deleted from the database forever.
	Syslog priorites range from 0-7 as follows:
		0 - System unusable
		1 - Immediate action required
		2 - Critical condition
		3 - Error conditions
		4 - Warning conditions
		5 - Normal but significant conditions
		6 - Informational messages
		7 - Debugging messages

Web Interface:
	Columns can be sorted by clicking their header.
	All messages in the database will be displayed with no filters.
	Priority must be an integer from 0-7 and will display all messages with a priority less than or equal to that.
	IP Address must be formatted as an IP but will search within the whole address
		Can contain only digits and dots
			-Must start with a digit
			-Can end with either	
		Example:
			10.86.90.1 will be found when searching for "10." or "90."
	All other fields support regular expressions and are case insensitive
	Messages are red for high-priority, orange for medium-priority, green for low-priority
	
GUI:
	Configuration
		Located at "File>Configuration"
		"Day to run database purge" is a number from 0-6 with 0 representing Monday.
		"Hour to run database purge" is a number from 0-23 with 0 representing 12am.
		After saving, the server must be restarted in order for the changes to take affect. The web interface paramaters, such as levels for priority highlighing, will be immediately noticeable.
	"Logs>Save Database To Logfile" has the same effect as the weekly purge (see General Information), except that the user chooses the name and location of the text file.
	"Logs>Load All From Database" will print all database messages to the GUI.
	"Logs>Load All From File" will allow you to select a previously saved file and print all messages from it to the GUI.
	Error messages are written to "syslog.exe.log" and an alert is generated.