RE: Excessive logging by the webserver

[Mario Goulart <mario@proxy.furg.br>]

Hi

On Tue, 20 Mar 2001, Charles Hall wrote:

> So as you say the solution would be to suppress hits to the web server
> from a specific host (i.e. the machine running glimpseindex) or run
> glimpseindex on the server machine itself.
> 
> Apache has a feature called "RefererIgnore" which might be what you
> need, but I'm no Apache expert and this particular feature seems to have
> been replaced by newer methods. Look here to see what I found:
> 
>     http://httpd.apache.org/docs/mod/mod_log_referer.html
> 
> Maybe you can decipher the Apache docs or find an Apache mailing list
> with more expertise. Or maybe there's some solution deep in the Glimpse
> website. Everyone who uses Glimpse like this must have the same
> problem. Or even on another search engine site like 'htDig', they do the
> same kind of indexing via server.

I've got a way to avoid the growing of apache's log file. 

You have to comment out the default (in my case) CustomLog directive

#CustomLog /usr/local/apache/logs/access_log common

and add the new ones:

SetEnvIf Host accessing.machine machine
CustomLog /dev/null common env=machine
CustomLog logs/access_log common env=!machine

Where accessing.machine is the machine witch is causing the undesirable
log entries. I'm not sure if it's a good idea to use /dev/null as output
to the log. But it works.

The mod_env.c and mod_log_config.c are needed (you can see witch modules
are compiled by running httpd -l).

Thanks for your help.

Regards.
Mario

> 
> > -----Original Message-----
> > From: Mario Goulart [mailto:mario@proxy.furg.br]
> > Entries like that full up the log files in the scanned 
> > machines. They are normal access logs, I know, but I was wondering if
> > there is a 
> > way to avoid logging accesses from the machine running webglimpse.
> > 
>