Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of minfrin@sharp.fm designates
 72.32.122.20 as permitted sender)
Message-Id: <768FEBC6-503A-431A-9219-7C2CE3AE6D94@sharp.fm>
From: Graham Leggett <minfrin@sharp.fm>
To: dev@httpd.apache.org
In-Reply-To: <E15FBC45-ED0C-4C35-8B7E-00B967F89549@rcbowen.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: RewriteLog and other per-module logging
Date: Tue, 21 Sep 2010 16:47:28 +0200
References: <E15FBC45-ED0C-4C35-8B7E-00B967F89549@rcbowen.com>

On 21 Sep 2010, at 4:26 PM, Rich Bowen wrote:

> So, I expect it's my own fault for not paying attention to this list  
> as closely as I once did, but ...
>
> Losing the ability to have a separate mod_rewrite log file will make  
> troubleshooting rewrite stuff so very much more difficult. Is there  
> anything planned for the ErrorLog directive that would let me do  
> something like:
>
> ErrorLog rewrite:/file/path
>
> so that different modules could have their own log files, in  
> addition to their own LogLevel settings?

+1.

While the separate logfile for rewrite was very evil, it was very  
useful to see logging from rewrite in one place.

Regards,
Graham
--