Op 28-07-10 15:41, Rainer Jung schreef:
On 28.07.2010 13:44, Dan Poirier wrote:
On 2010-07-28 at 03:51, Alex Wulmsalex.wu...@scarlet.be wrote:
Hi,
While adding some debug log statements to a module I'm working on, I
ran
into the problem that ap_log_error (in apache 2.2) does not support
Hi,
While adding some debug log statements to a module I'm working on, I ran
into the problem that ap_log_error (in apache 2.2) does not support %zd
or %zu conversion for type_t arguments. This was problematic to make the
code compile on both 32 and 64 bit platforms. So I made a small wrapper
On 2010-07-28 at 03:51, Alex Wulms alex.wu...@scarlet.be wrote:
Hi,
While adding some debug log statements to a module I'm working on, I ran
into the problem that ap_log_error (in apache 2.2) does not support %zd
or %zu conversion for type_t arguments. This was problematic to make the
code
On 28.07.2010 13:44, Dan Poirier wrote:
On 2010-07-28 at 03:51, Alex Wulmsalex.wu...@scarlet.be wrote:
Hi,
While adding some debug log statements to a module I'm working on, I ran
into the problem that ap_log_error (in apache 2.2) does not support %zd
or %zu conversion for type_t arguments.
On Wednesday 21 July 2010, William A. Rowe Jr. wrote:
On 7/21/2010 4:35 PM, Stefan Fritsch wrote:
And I agree that a unified logging formatter would be nice, but
this is not something that will be done before 2.3.7 and it
would likely mean an incompatible API change for modules
providing
On 20.07.2010 21:14, Stefan Fritsch wrote:
On Tue, 20 Jul 2010, Rainer Jung wrote:
message and behind the message. I guess you can get rid of the latter
split by assigning a format specifier also to the log message, like
'%M' or similar, and then
ErrorLogFormat [%{u}t] [%l] [pid %P%{:tid }T]
-Original Message-
From: Rainer Jung
Sent: Mittwoch, 21. Juli 2010 11:24
To: dev@httpd.apache.org
Subject: Re: Error log format configuration syntax
On 20.07.2010 21:14, Stefan Fritsch wrote:
On Tue, 20 Jul 2010, Rainer Jung wrote:
message and behind the message. I guess
On 7/20/2010 2:14 PM, Stefan Fritsch wrote:
- taking all adjacent non-whitespace as prefixes and suffixes,
collapse resulting adjacent whitespace in the output by adding the
whitespace in front of the prefix to the prefix and dropping leading
whitespace from the resulting line)
On Wednesday 21 July 2010, William A. Rowe Jr. wrote:
On 7/20/2010 2:14 PM, Stefan Fritsch wrote:
- taking all adjacent non-whitespace as prefixes and suffixes,
collapse resulting adjacent whitespace in the output by adding
the whitespace in front of the prefix to the prefix and
dropping
On 7/21/2010 4:35 PM, Stefan Fritsch wrote:
And I agree that a unified logging formatter would be nice, but this
is not something that will be done before 2.3.7 and it would likely
mean an incompatible API change for modules providing handlers for
mod_log_config. IMHO, this can wait until
On 7/21/2010 4:35 PM, Stefan Fritsch wrote:
On Wednesday 21 July 2010, William A. Rowe Jr. wrote:
On 7/20/2010 2:14 PM, Stefan Fritsch wrote:
- taking all adjacent non-whitespace as prefixes and suffixes,
collapse resulting adjacent whitespace in the output by adding
the whitespace in front
On 20.07.2010 00:39, Stefan Fritsch wrote:
Hi,
I have been working on making the error log format configurable. It's
more or less working now, but I could use some feed-back about the
config syntax. The difficulty is that many tokens only produce output in
some situations (e.g. no remote IP in
On Tue, 20 Jul 2010, Rainer Jung wrote:
message and behind the message. I guess you can get rid of the latter split
by assigning a format specifier also to the log message, like '%M' or
similar, and then
ErrorLogFormat [%{u}t] [%l] [pid %P%{:tid }T] %F: %{}{: }E%{[client }{] }a
%M %{}{,
Hi,
I have been working on making the error log format configurable. It's more
or less working now, but I could use some feed-back about the config
syntax. The difficulty is that many tokens only produce output in some
situations (e.g. no remote IP in server scope, no thread id in a
14 matches
Mail list logo
