From owner-freebsd-apache@FreeBSD.ORG  Thu May 26 20:14:26 2011
Return-Path: <owner-freebsd-apache@FreeBSD.ORG>
Delivered-To: freebsd-apache@FreeBSD.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id C5170106564A;
	Thu, 26 May 2011 20:14:26 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org
	[IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id C245F15FA43;
	Thu, 26 May 2011 20:13:46 +0000 (UTC)
Message-ID: <4DDEB479.4020609@FreeBSD.org>
Date: Thu, 26 May 2011 13:13:45 -0700
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10
MIME-Version: 1.0
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
References: <4DDC9B15.2090703@FreeBSD.org>
	<20110525072552.GA31990@icarus.home.lan>
In-Reply-To: <20110525072552.GA31990@icarus.home.lan>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-apache@FreeBSD.org, alfred@freebsd.org
Subject: Re: Interesting apache 2.2 + accept filter problem
X-BeenThere: freebsd-apache@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Support of apache-related ports  <freebsd-apache.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-apache>, 
	<mailto:freebsd-apache-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-apache>
List-Post: <mailto:freebsd-apache@freebsd.org>
List-Help: <mailto:freebsd-apache-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-apache>,
	<mailto:freebsd-apache-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 20:14:26 -0000

On 05/25/2011 00:25, Jeremy Chadwick wrote:
> It doesn't seem to harm anything from what I can tell.

Thanks for the response. It would be helpful to have some verification 
that the error message is not harmful, or better yet, how can we make it 
go away? :)


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/