RE: Excessive logging by the webserver

[Charles Hall <Charles.Hall@sas.com>]

> -----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.
<snip>

Oh, I think I see. Well, actually your symptom is related to "glimpse", not webglimpse. Webglimpse is merely the front-end to the Glimpse database, and these hits are "glimpseindex.php" hits across the network. ('wgreindex' calls glimpseindex.)

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.

Good luck!

Charles Hall
Raleigh, NC

> -----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.
>