On Monday 13 September 2010, Sergio Junqueira wrote:
> >Do you need the first entry to determine which request may have
> >caused httpd to crash or is there a different reason?
>
> Mod_log_forensics writes the log record as soon as it is received.
> Mod_log_config writes the log record after the
onse was sent or if
the request failed.
Thanks,
From: Igor Galić <@brainsware.org>
To: dev@httpd.apache.org
Sent: Mon, September 13, 2010 3:51:47 AM
Subject: Re: Apache logging
- "Sergio Junqueira" <@yahoo.com> wrote:
>
- "Sergio Junqueira" wrote:
> >Do you need the first entry to determine which request may have
> caused httpd to crash or is there a different reason?
>
>
> Mod_log_forensics writes the log record as soon as it is received.
> Mod_log_config writes the log record after the response is avail
From: Sergio Junqueira
Sent: Sunday, September 12, 2010 8:35 PM
To: dev@httpd.apache.org
Subject: Re: Apache logging
>Do you need the first entry to determine which request may have caused
httpd to crash or is there a different reason?
Mod_log_forensics writes the log record as soon as it is receive
September 12, 2010 7:18:07 AM
Subject: Re: Apache logging
On Fri, 10 Sep 2010, Sergio Junqueira wrote:
> I have a suggestion for the developers of Apache related to mod_log_config or
> mod_log_forensics:
>
> 1) To allow mod_log_config to write the log file with a first log entry w
On Fri, 10 Sep 2010, Sergio Junqueira wrote:
I have a suggestion for the developers of Apache related to mod_log_config or
mod_log_forensics:
1) To allow mod_log_config to write the log file with a first log entry with
basic information about the request before it's processed further (that is,
I have a suggestion for the developers of Apache related to mod_log_config or
mod_log_forensics:
1) To allow mod_log_config to write the log file with a first log entry with
basic information about the request before it's processed further (that is,
after receiving the headers). The second log
2009/4/15 Michele Waldman :
> ./server/util_script.c
>apr_table_addn(e, "REMOTE_USER", r->user);
>apr_table_addn(e, "REDIRECT_REMOTE_USER", back->user);
>
> I could this. Is this the right place?
That's for ENVs, but not the place where a module reads and sets the
user to