Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@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, 28 Nov 2011 14:39:42 -0000 (UTC)
From: Igor =?utf-8?Q?Gali=C4=87?= <i.galic@brainsware.org>
To: docs@httpd.apache.org
Subject: Re: Error codes
Message-ID: <a62aec7b-c3f5-43a8-8807-8a2626b733cc@iris>
In-Reply-To: <B3707F2B-24EE-490B-8DF4-6419A2E81D1D@rcbowen.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


----- Original Message -----
> For those of you who don't follow dev@ closely, please take a look at
> http://markmail.org/message/tltkphtp327kep6i
> 
> 
> Summary: I'd like to put error codes, of the form AH1234 (AH =3D Apache
> httpd and 1234 is an arbitrary number) into the calls to
> *_log_?error so that we can have per-error detailed documentation
> that is easily Google-able.
> 
> 
> This is a multi-step process that looks like this:
> 
> 
> 1) Create file in svn that lists sequential error codes so that we
> know what the next number is. The file should list error code and
> the file in which it is used. Should probably also list line number,
> although that changes over time, so it's approximate.
> 2) Find all calls to *_log_?error (Stefan says there's 2700+ such
> calls!) and add the next error code to the beginning of the message.
> In parens, perhaps?. Update the file in #1.
> 3) Add a description of the error condition, and if known, the
> remediation, to the Wiki. Update the file in #1 with the URL of that
> document. We probably want one URL per error code. We're counting on
> the error code being unique-enough to be google-able, so the actual
> URL doesn't matter a lot at this point.

  http://s.apache.org/AH1234

The only question would be, what to point that to :)  

> 4) Eventually, when we have a good body of these error documents, we
> should figure out where they fit in the official documentation, and
> move them there, complete with a style sheet and standard page
> elements. (Module, error_level, message, meaning, remediation, etc.)
> 
> 
> Presumably we would do this initially in trunk, and based on how well
> the effort goes, we can propose patches for 2.4 and 2.2.
> 
> 
> Comments?
> 
> 
> 
> 
> 
> 
> 
> --
> Rich Bowen
> rbowen@rcbowen.com :: @rbowen
> rbowen@apache.org


-- 
Igor Gali=C4=87

Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515  2EA5 4B1D 9E08 A097 C9AE


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org