Addressed to: Alex Black <[EMAIL PROTECTED]>
[EMAIL PROTECTED]
** Reply to note from Alex Black <[EMAIL PROTECTED]> Sun, 14 Jan 2001 17:06:39
-0800
>
> the problem with that is as soon as you run a load-baanced
> installation, collecting apache logs start to be a pain in the a$$ :)
>
I am pretty sure you can just run webalizer on the logfiles from each
of your servers and obtain a combined logfile. I think it might be as
easy as not using incremental mode. I think I remember seeing
something about this being covered somewhere in the Webalizer docs. It
might also be a matter of using incremental mode. I don't remember.
You will have to take care not to feed the same file twice. It has
been a long time since I setup my Webalizer, but I have asked the autor
for clarification. I will forward the response when I get it.
Another feature I like, you can turn off hostname lookups in Apache and
have Webalizer do them when it analyzes the logs. It also caches
those DNS lookups as it runs. This dresticly reduces the number of
DNS requests, and there is no cost at all on the people hitting the
web site(s).
> I have given some thought to the logging thing, but am still
> undecided re: letting apache do its thing, and writing scripts to
> aggregate the logs, or turning off apache logging and going to the
> DB.
>
> problem is this puts an annoying amount of stress on the production
> DB, so there you have it, the dilemma :)
IMHO, the best solution will minimize the delay added to visitiors to
the site. If it takes too much processing power you can always analyze
the web files on a separate machine so visitiors never are
inconvienenced. I just run Webalizer at night when my hit counts are
low.
Rick Widmer
Internet Marketing Specialists
http://www.developersdesk.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
