NAME

	htsync - a mysql database <-> htdig config file synchronizer


SYNOPSIS

	htsync <htsync_cfg> <customer_cfg>


DESCRIPTION

	htsync will maintain consistent data between htdig configurations
 	and a mysql database

	The setup for the database is included in htsync, i.e. if the tables
	are not present, they will be created by htsync. The database itself
	and username/password information must be specified in the htsync
	configuration file <htsync_cfg>:

	db_name: 	<the name of the database you created for htdig conf>
	db_user:	<the username that can connect to db_name>
	db_pass:	<the password of db_user>

	When htsync is invoked with a specified customer configuration file
	in the usual htdig configuration format, it will read the contents
	of that file and test whether an updated value is stored in the 
	database, for example by a webinterface. If it finds an updated value,
	it will save that back to the configuration file.

	On the other hand, if the configuration file has been modified after
	a certain value is stored in the database, the database value will be
	updated. This way, the synchronization works both ways.

	As an extra, htsync gathers some basic statistics about the indexes
	such as index file size, last modification of the indexes and stores
	this in the database as well. 

	htsync also tries to determine and replicate to mysql the crontab 
	entry for the given customer by reading the crontab of the user that 
	is specified in the <htsync_cfg>:

	cron_user:	<the account that has crontab entries for htdig>

	If you do not have crontab entries or you just don't care, fill in
	some bogus stuff and htsync will skip with a warning.
 
	Typically, htsync should be run from crontab itself to be able to 
	maintain the indexes on a regular basis, especially if the database 
	is liable to change for example by customers who update their own 
	database entries in a web interface.


BUGS

	Their is a maximum line length for the configuration file that htsync
	can handle. It is defined in config.h, and it is not specifically 
	checked on, so possible overflows may happen here if database updates
	exceed this length.


FILES
	
	htsync.cfg
	<customer>.conf


AUTHOR

	JP <jprins@dds.nl>
	

DISCLAIMER

	Please note that this program is being given to you as is, and I will
	not be held liable for any damage or problems that may occur as a
	result of using the program.