Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of i.galic@brainsware.org
 designates 188.40.115.121 as permitted sender)
Date: Mon, 13 Sep 2010 06:51:47 +0000 (UTC)
From: =?utf-8?Q?Igor_Gali=C4=87?= <i.galic@brainsware.org>
To: dev@httpd.apache.org
Message-ID: <1953819905.2230.1284360707232.JavaMail.root@iris>
In-Reply-To: <252802.94693.qm@web120102.mail.ne1.yahoo.com>
Subject: Re: Apache logging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


----- "Sergio Junqueira" <sjjrbhz2@yahoo.com> wrote:

> >Do you need the first entry to determine which request may have
> caused httpd to crash or is there a different reason?
>=20
>=20
> Mod_log_forensics writes the log record as soon as it is received.
> Mod_log_config writes the log record after the response is available.
> I don=C2=B4t want to miss information about any request. Its important to
> identify all incoming requests, no matter if they fail or succeed.
>=20
>=20
> I would like to trace them having a small log record from the incoming
> requests. Useful to determine which request may have caused httpd to
> crash, as you mentioned, and to have 100% guarantee that all incoming
> requests were logged before Apache started processing it.


Have you already exhausted other methods such as mod_whatkilledus?

bye,
i
--=20
Igor Gali=C4=87

Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/