Re: Modlogan newbie questions

Hi,

> 1) Hostname is probably the setting you should define in the config file.

be careful not to confuse the setting for the "modlogan" output plugin
and the "template" plugin - set the right one. You won't find the
"correct" option for the template plugin by just looking at the list
of available options - it's just one variable like others for this
plugin.
I don't remember the option, maybe something like variable HOSTNAME,whateve=
r.com
You can get the variable names by looking at the template. Different
templates can have different variable names.

> 2) Your apache server most likely logs IP adresses. You'd need to setup
> revese DNS resolution to enable those stats on countries and TLDs. This
> has a CPU cost which, on large log files, would need to be taken into
> account.

It's not so much about CPU costs, but delays. Some DNS servers will be
unreachable, resulting in timeouts when resolving the names. When you
have a really big site, resolving the logfiles may take longer than
new hits come in...
So for bigger sites you should really look for an optimized logfile resolve=
r.
I'm using jdresolve, and it's working pretty good. It can process
multiple lines in parallel (well, almost every log resolver can do
that), but it also uses a cache database, and it will try to do
class-c resolving, too - so even if an IP is unknown, you might get
useable domain names, at least for bigger networks.

best regards,
Erich Schubert
--
    erich@(mucl.de|debian.org)      --      GPG Key ID: 4B3A135C    (o_
  To understand recursion you first need to understand recursion.   //\
  Wo befreundete Wege zusammenlaufen, da sieht die ganze Welt f=FCr   V_/_
        eine Stunde wie eine Heimat aus. --- Herrmann Hesse