Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 91617 invoked by uid 500); 24 May 2003 18:58:33 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 91604 invoked from network); 24 May 2003 18:58:32 -0000 Message-ID: <3ECFC126.4020603@attglobal.net> Date: Sat, 24 May 2003 14:59:50 -0400 From: Jeff Trawick Reply-To: trawick@attglobal.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: ErrorLog/VirtualHost Modification References: <5.2.0.9.2.20030524074740.03c6cdc0@pop3.rowe-clan.net> <1053787810.6181.43.camel@ninja.dilbert.dns> In-Reply-To: <1053787810.6181.43.camel@ninja.dilbert.dns> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Alasdair Lumsden wrote: > On a busy server with many VirtualHosts, the common ErrorLog is totally > useless. > > However, if you could customise it, and add the VirtualHost ServerName > (as you can with CustomLog %v), then the common ErrorLog suddenly > becomes VERY useful. with 2.0, a custom module can implement an error log hook and format data however it wants... the error log hook is passed the server_rec, so the vhost can be identified yes, it would take some lines of code, but not very many