Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Date: Wed, 3 May 2000 13:49:25 -0700
From: bmartin@penguincomputing.com
To: new-httpd@apache.org
Subject: Re: Doh!! scrap that last patch
Message-ID: <20000503134925.A21752@joe.penguincomputing.com>
References: <20000502162648.A1296@joe.penguincomputing.com>
 <20000502164640.A1510@joe.penguincomputing.com>
 <005501bfb502$189456c0$c1e01b09@raleigh.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <005501bfb502$189456c0$c1e01b09@raleigh.ibm.com>

On Wed, May 03, 2000 at 09:18:39AM -0400, Bill Stoddard wrote:
> Your patch does this:
> 
> ap_log_rerror(APLOG_MARK, APLOG_NOERRNO|APLOG_ERR, 0, r, "DB user %s: authentication
> failure for \"%s\": %s",  r->user, r->uri, ap_strerror(invalid_pw, error_buf, 1024));
> 
> You can accomplish pretty much the same thing (in a more normal Apache fashion) with:
> 
> ap_log_rerror(APLOG_MARK, APLOG_ERR, invalid_pw, r,  "DB user %s: authentication failure
> for \"%s\",  r->user, r->uri);
> 
> If you specify APLOG_ERR then pass in the status code, ap_log_rerror will call ap_strerror
> under the covers.
> 
Cool.  I didn't know that.  This stuff isn't documented is it?
I suppose it is probably somewhat premature to start talking about documentation :)

Brian