Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4C867F8D.1050906@rowe-clan.net>
Date: Tue, 07 Sep 2010 13:08:13 -0500
From: "William A. Rowe Jr." <wrowe@rowe-clan.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: Configurable error log format
References: <201008182031.45169.sf@sfritsch.de>
 <201009051749.06927.sf@sfritsch.de>
In-Reply-To: <201009051749.06927.sf@sfritsch.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 9/5/2010 10:49 AM, Stefan Fritsch wrote:
> On Wednesday 18 August 2010, Stefan Fritsch wrote:
>> I intend to commit it to trunk after I have written some docs and
>> 2.3.7 is tagged. It duplicates some code from mod_log_config. If
>> there are enough people interested in unifying the log formaters
>> for access and error logs, we can do that work in trunk.
>> Personally, I don't think it's necessary for 2.4.
> 
> This took a bit longer than anticipated but it is now commited to 
> trunk. There are a still a few open issues but those can be resolved 
> while the code receives more testing in trunk:
> 
> - there is no way yet to match the default format's behaviour of 
> logging the source file info only for loglevel debug and higher

Just a thought; we have %nnn{}x syntax today, what about overloading the
concept of %test codes with numeric 0-7 error levels?  I was thinking
about allowing verbose levels, but obviously '%debug' would immediately
trip up that theory :)