I like httplog <http://www.gnu.org/directory/all/httplog.html>
It doesn't resolve DNS names for you, but it does handle rolling over files, with suitable naming and gzip compression. Presumably you could put another program in the output chain to do the DNS resolution on the fly. That would mean that you wouldn't get the latency problems associated with resolving IPs before the request is processed, but you would have resolved IPs in your logs right from when they are written. The key thing with DNS resolvers is that to operate at an acceptable speed they need to cache results, and to run multiple DNS requests in parallel. The perl script jdresolve <http://jdrowell.com/projects/jdresolve> might do you for the name resolution, but if it was me I'd modify it so that it only concerns itself with the first field in the http logs. There must be something around in C or C++ to do this job well. Andrew McNaughton On Thu, 17 Jul 2003, Voytek Eymont wrote: > Date: Thu, 17 Jul 2003 23:57:09 > From: Voytek Eymont <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [SLUG] Apache vhost logs managemt > > I'm setting up Apache 1.3x with name vhost and I need to set up log > handling for all vhosts; basically, I'd like to is: > > process yesterday's logs to resolve IP addresses; > gzip yesterday's logs (is bzip2 what should be used instead of gzip ?); > have logs saved with some sort of dd-mm-yy > > suggestions and useful scripts welcomed > > thanks, > > Voytek Eymont > -- No added Sugar. Not tested on animals. May contain traces of Nuts. If irritation occurs, discontinue use. ------------------------------------------------------------------- Andrew McNaughton In Sydney Working on a Product Recommender System [EMAIL PROTECTED] Mobile: +61 422 753 792 http://staff.scoop.co.nz/andrew/cv.doc -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
