> Now, the idea of scanning the local logile and updating > chunks at a time... this could be also a viable solution.
We do this today on a nightly basis as a solution to providing separate traffic reports for each of our "virtual hosts" (in quotes because to us, our virtual hosts are more like subsites from openacs). Our process works by: * Appending a subsite identifier to each log entry. We use the extendedheaders parameter of the nslog module and a filter on page requests to set the appropriate subsite identifier. * Running a perl script over the local aolserver log file generating one log file per subsite. This has worked well for us for over a year now. We like keeping a single master local log file as it is: * easier to backup (one file vs. many) * simple to process to generate a master traffic log report * in sequential order - we still are use the aolserver-errors.pl perlscript (http://cvs.openacs.org/cvs/openacs.org-dev/packages/monitoring/bin/aolserver-errors.pl) to process our log for errors that occur outside of page requests (and this script depends on the entries in the log file being sequential). -Mike -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
