Aengus wrote:
Kevin Murphy <[EMAIL PROTECTED]> wrote:
In that case, the second apparent binary run
of analog did not run with FROM or TO set at all, which caused a
horribly slow scan of all log files.
I don't have any suggestions as to why Analog is running twice for you,
but I don't think it's an Analog problem
Yes, I didn't think so. I just hoped it might ring a bell with somebody.
have you looked at the Access log to see if there is one or 2
requests to analog.pl?
Yeah, there's just a single POST request showing in the log file.
But I did want to point out that having FROM and TO set won't
necessarily speed up Analog, as it will still have to read all specified
log files to find entries that fall between your FROM and TO.
Actually, I wrote a Perl module to dynamically create the minimal set of
LOGFILE statements based on the FROM and TO values (my Apache logs are
named chronologically, cut by month or day). The module understands
Analog FROM and TO syntax and populates a LOGFILE template to generate
the actual LOGFILE names. I've tested it, and it does speed up Analog
quite a bit, as long as I can beat this double invocation problem.
When I run analog manually on the command line with the same variables
passed in my CGI test (with +gtest_var_settings.cfg), I can see only one
run of analog, not surprisingly. I was wondering initially if analog
was recursively invoking itself for some strange reason.
I will reexamine the Apache httpd.conf file to see if there's any funny
business going on.
-Kevin Murphy
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------
