On Thu, 18 Oct 2001, Aengus wrote: > From: <[EMAIL PROTECTED]> > > > I've been trying to get a report for a single virtual host out of a > > logfile which contains line for many virtual hosts, as well as some > > with no virtual host information. > > The relevant bits of the config file I've got are: > > LOGFORMAT COMBINED > > LOGFILE /usr/local/var/log/httpd-access.log* > > FILEINCLUDE / > > FILEINCLUDE /~warped/* > > VHOSTINCLUDE http://www.warped.man.ac.uk/ > > VHOST entries don't usually include the http:// > > > Sometimes the pages are accessed as www.compsoc.man.ac.uk/~warped/* > > othertimes as www.warped.man.ac.uk/* > > VHOST entries don't have anything to do with what the user specified - > they're usually part of the server configuration.
A person looking at the pages can stick either of the above into their browser to get at the same physical files. > > I've trie *www.warped.man.ac.uk* and many other things as the > VHOSTINCLUDE > > line, but I'm stumped. > > It might help if you posted a couple of lines from your logs - it sounds > like you're trying to use something else as your vhost field. altex.demon.co.uk - - [14/Oct/2001:01:30:57 +0100] "GET /WARPED/contents.html HTTP/1.0" 200 3698 "http://www.warped.man.ac.uk"; "Mozilla/5.0 (compatible; Konqueror/2.1.1; X11)" altex.demon.co.uk - - [14/Oct/2001:01:30:57 +0100] "GET /WARPED/cover.html HTTP/1.0" 200 838 "http://www.warped.man.ac.uk"; "Mozilla/5.0 (compatible; Konqueror/2.1.1; X11)" Thta is from someone getting the file through the warped vhost, but they can also generate lines like below if not using the vhost path. ddslppp164.eugn.uswest.net - - [14/Oct/2001:12:26:31 +0100] "GET /~warped/the_commitee/DAVO.jpg HTTP/1.1" 200 26766 "http://www.compsoc.man.ac.uk/~warped/the_commitee/"; "Mozilla/4.0 (compatible; MSIE 6.0b; Windows NT 5.1; Hotbar 3.0)" > > The logging can't be changed to a seperate log for this virtual host, > and > > there's ~1.8GB of them from the last 6 months or so, so cheating and > > running them through grep first isn't an option. > > Why not? grep should chew through 1.8G of logs in a few minutes. (I just > went through about 400M of logs in about 90 seconds on a PIII600). The webserver is a P166MMX with 32MB of ram, and not that much diskspace. And runs the webserver and has a load average of ~.4 most of the time.. so I'd prefer to avoid flooring the machine really. John Gilbertson -- I love you coffee; You make me glow. You make me smile. I love you so. My nerves don't like you, but what do they know? - Garfield, 1/10/1982 +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
