From owner-freebsd-chat  Fri Feb  2 14:36:49 2001
Delivered-To: freebsd-chat@freebsd.org
Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5CE7A37B4EC; Fri,  2 Feb 2001 14:36:20 -0800 (PST)
Received: (from daemon@localhost)
	by smtp02.primenet.com (8.9.3/8.9.3) id PAA09085;
	Fri, 2 Feb 2001 15:30:30 -0700 (MST)
Received: from usr08.primenet.com(206.165.6.208)
 via SMTP by smtp02.primenet.com, id smtpdAAAcLaiFr; Fri Feb  2 15:30:12 2001
Received: (from tlambert@localhost)
	by usr08.primenet.com (8.8.5/8.8.5) id PAA15731;
	Fri, 2 Feb 2001 15:35:56 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <200102022235.PAA15731@usr08.primenet.com>
Subject: Re: per machine access logs in Apache
To: steve@FreeBSD.ORG (Steve Price)
Date: Fri, 2 Feb 2001 22:35:56 +0000 (GMT)
Cc: chat@FreeBSD.ORG
In-Reply-To: <20010202154728.I15902@dorado.freebsd.org> from "Steve Price" at Feb 02, 2001 03:47:28 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-chat@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Has anyone come up with a slick way of getting per machine access
> logs in Apache?  Here's the scenario so that the question will make
> more sense.

You should look at the Apache FAQ; if you have just installed
Apache, the first page that comes up links to documentation
that was installed on your local machine, and includes the FAQ
in HTML format.

This is covered in detail.

The general issue you are going to have is whether you want it
based on host-where-apache-is-running or host-apache-is-serving.
The "running" case is a lot easier; in the other case, you can
quickly run out of logging file descriptors (per the FAQ).

Actually, we invented something called "syslog" a very long time
ago, to deal with exactly this problem.  8-).  Too bad Apache
has rolled their own.

FWIW, for the virtual host case, you can change the log format
to cause it to log the virtual host name, etc..  For the other
case, you must be having the problem because you are running a
shared filespace, mounted on multiple servers.  The best answer
is "don't do that"; the second best answer is "you can do that,
if you realize that your throughput will be bottlenecked at the
access to your shared filespace, so lots of servers do you little
good; if you insist, putting the host name in the log file name
is covered in the FAQ".


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message