Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Mon, 24 Jun 2002 08:19:24 -0700 (PDT)
From: Rasmus Lerdorf <rasmus@apache.org>
To: Ryan Bloom <rbb@covalent.net>
cc: dev@httpd.apache.org
Subject: RE: Apache 2.0 Numbers
In-Reply-To: <017e01c21b92$51f374c0$0a01230a@KOJ>
Message-ID: <Pine.LNX.4.44.0206240816460.2711-100000@www.lerdorf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

> > What is the correct way to fail in a filter post_config?  Do I return
> -1
> > from it if my filter finds a fatal error?  I can't use ap_log_rerror()
> at
> > this point, right?  How would I log the reason for the failure?
>
> I'm confused by the question, but I'll try to answer.  If you mean the
> post_config phase, then you can use ap_log_error or ap_log_perror.  If
> you want to stop the server from starting, just return DECLINED.

Right, I found ap_log_error.  It was the return value I was looking for.
None of the example filter modules had a fatal error check at the config
phase.  So returning a -1 is the correct way to stop the server from
starting.  Thanks.

-Rasmus