Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 60487 invoked from network); 16 Jun 2004 06:19:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 16 Jun 2004 06:19:31 -0000 Received: (qmail 36330 invoked by uid 500); 16 Jun 2004 06:19:55 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 36300 invoked by uid 500); 16 Jun 2004 06:19:54 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 36286 invoked by uid 99); 16 Jun 2004 06:19:54 -0000 Received: from [80.229.52.226] (HELO hugin.webthing.com) (80.229.52.226) by apache.org (qpsmtpd/0.27.1) with ESMTP; Tue, 15 Jun 2004 23:19:54 -0700 Received: by hugin.webthing.com (Postfix, from userid 500) id 99BB63E28C; Wed, 16 Jun 2004 07:19:11 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by hugin.webthing.com (Postfix) with ESMTP id 5E7953DB61 for ; Wed, 16 Jun 2004 07:19:11 +0100 (BST) Date: Wed, 16 Jun 2004 07:19:11 +0100 (BST) From: Nick Kew To: httpd-dev Subject: Re: [PATCH] mod_unique_id: Keep running w/ Broken DNS In-Reply-To: <1087351955.16238.20.camel@localhost> Message-ID: References: <1087351955.16238.20.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Tue, 15 Jun 2004, Paul Querna wrote: > I see three ways to solve this issue: > 1) Make the error we spit out more verbose when DNS is broken. +1 on that. Error message should suggest that luser disables the module. > 2) Continue running, turning off mod_unique_id. Violates KISS (slightly), and keeps the module loaded as deadweight. > 3) Complain to upstream vendors.(don't enable mod_unique_id by default!) Good idea, but we don't really control that unless we adopt DJB-style licensing. > No matter what is done, It would be nice to have some sort of change > into 2.0.50 before a release is made. Indeedie. -- Nick Kew