From dev-return-26858-apmail-httpd-dev-archive=httpd.apache.org@httpd.apache.org Sat Mar 02 19:06:26 2002
Return-Path: <dev-return-26858-apmail-httpd-dev-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-dev-archive@httpd.apache.org
Received: (qmail 13027 invoked by uid 500); 2 Mar 2002 19:06:26 -0000
Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
list-help: <mailto:dev-help@httpd.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@httpd.apache.org>
list-post: <mailto:dev@httpd.apache.org>
Delivered-To: mailing list dev@httpd.apache.org
Received: (qmail 13014 invoked from network); 2 Mar 2002 19:06:25 -0000
Reply-To: <rbb@covalent.net>
From: "Ryan Bloom" <rbb@covalent.net>
To: <dev@httpd.apache.org>
Subject: RE: Log file rotation... log sub system
Date: Sat, 2 Mar 2002 11:05:06 -0800
Organization: Covalent Technologies
Message-ID: <004601c1c21d$2ab8d180$0a01230a@KOJ>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <003301c1c1f8$e338b880$6401a8c0@sashimi>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> > dirkx@covalent.net wrote:
> >
> > > Though I one 100% agree with the stance that a proper web server
> should..
> > > well.. serve pages - It sure would be nice if we could have a
logging
> > > subsystem in apache 2.1 or higher which took care of some of the
> harder
> > > things for us module/appserver developers when bouncing around
> > > logging data.
> >
> > In v2.0, mod_proxy, mod_cache, mod_ldap and mod_dav all support
"sub"
> > modules beneath them to perform specific tasks (eg mod_disk_cache
and
> > mod_mem_cache for mod_cache, etc).
> >
> > Perhaps the logging module should be split up in the same way, with
> > mod_log handling the hooks, and mod_log_disk handling logging direct
to
> > disk, mod_log_sql handling direct to database, etc.
> >
> > Each logging submodule could allow "drop through" the way mod_cache
does
> > - so if mod_log_sql cannot handle a log for any reason, through
config
> > or through failure, it could drop through to mod_log_disk and not
get
> > lost.
> 
> Wouldn't just making ap_log_error() ap_run_log_error() solve a lot of
> these problems?

ap_log_error_core already runs a hook to allow module to do more with
the error log, so this is effectively already done.

Ryan