path: root/README

$Id: README,v 1.3 2001/12/07 03:52:56 helios Exp $


Homepage
--------
http://www.grubbybaby.com/mod_log_mysql/



Approach
--------

In order to save speed and overhead, links are kept alive in between
queries.  This module uses one SQL link per httpd process.  Among other
things, this means that this module supports logging into only one
MySQL server, and for now, also, only one SQL database (although the
latter limitation can be relatively easily removed). 

Different data can be sent to different tables.  i.e., it's possible to
define one table for TransferLog, one for RefererLog, and a 3rd for
AgentLog.  [ Note: this is now deprecated behavior.  Please consider
logging Agent and Referer to the same table as your transfers. ]

Virtual hosts are supported in the same manner they are in the regular
logging modules.  If you specify a different table for a virtual
host it will be used, otherwise the 'general' would be used.  Note:
since all 3 types of logs are implemented within the same module, if
you specify an overriding table for a virtual host for one type of log,
it'll ignore any previous 'general' defaults (see the example in the
end).

SQL links are opened on demand (i.e., the first time each httpd needs
to log something to SQL, the link is opened).  In case the SQL server
is down when trying to connect to it, the module remains silent and
logs no error (I didn't want thousands of error messages in the
logfile).  In case the SQL link is broken ("mysql server has gone
away") a proper error message is kept to the error log (textual :), and
the module tries to reestablish the concact (and reports whether it
succeeded or not in the error log).  If the link cannot be
reestablished, the module wil Christopher Powell