Hello!

I am going to be setting up Analog to do stat analysis for customer vhost
accounts on my Unix based server. To do this, I'd planned on using the cache
option and wanted to know if there were any potential problems using cache
files in one of the following manners and which should be considered the
best method:

Scenario One:
-------------
At the end of every day, read in and analyze the old cache files and the new
log file in one operation - creating a new cache file. (my question: Does
analog create the new cache file from just the new log data or from the old
cache files AND the new log data - thereby creating the possibility for
double counting)

Scenario Two:
-------------
At the end of every day, read in and analyze the new log file, create a
cache file for it and build the report from all the cache files. (would I
need to have two analog.cfg files for this? One to generate the cache file
and a second to analyze all the cache files?)

I would like to reset my log files at least once a week and - in a perfect
world - nightly to conserve on file space. I am dealing with a large number
of virtual hosted accounts and keeping log files for all them over extended
periods of time is simply not possible given space constraints (some of
these sites are very busy).

Furthermore, I don't suppose there is a way to have one cache file
containing all of the information from previous analysis that is appended to
as time goes on.

Your help is appreciated.

Thanks;


Michael R. Bagnall
Powertools Productions, LLC.
Internet Development, Design, Programming & Hosting
615.453.1141 - 800.444.1563 (toll-free)

[EMAIL PROTECTED]
http://www.powertools.net

------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------

Reply via email to