From owner-freebsd-current@FreeBSD.ORG Tue Apr 22 22:40:17 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74B0F106566B; Tue, 22 Apr 2008 22:40:17 +0000 (UTC) (envelope-from fbsd-current@mawer.org) Received: from outbound.icp-qv1-irony-out3.iinet.net.au (outbound.icp-qv1-irony-out3.iinet.net.au [203.59.1.148]) by mx1.freebsd.org (Postfix) with ESMTP id C5A038FC24; Tue, 22 Apr 2008 22:40:16 +0000 (UTC) (envelope-from fbsd-current@mawer.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvwAAE4DDkjLzq3r/2dsb2JhbAAIrS0 X-IronPort-AV: E=Sophos;i="4.25,696,1199631600"; d="scan'208";a="253282757" Received: from unknown (HELO [10.24.1.1]) ([203.206.173.235]) by outbound.icp-qv1-irony-out3.iinet.net.au with ESMTP; 23 Apr 2008 06:30:03 +0800 Message-ID: <480E6698.7000008@mawer.org> Date: Wed, 23 Apr 2008 08:28:40 +1000 From: Antony Mawer User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Poul-Henning Kamp References: <13383.1208899946@critter.freebsd.dk> In-Reply-To: <13383.1208899946@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, d@delphij.net, Ivan Voras Subject: Re: Http Accept filters (accf_http) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2008 22:40:17 -0000 Poul-Henning Kamp wrote: > In message <480E589C.8010108@delphij.net>, Xin LI writes: > >> | Does anyone know why accf_accept is disabled by default in the ports' >> | stock Apache 2.2 (it's disabled in the default config files)? I thought >> | it was because it was dangerous or flawed for some reason, though (at >> | least for light loads comparable to those of OP) it seems to work fine. > > I think adding them to the apache is OK, as long as apache fails > gracefully if they are not present in the kernel. I seem to recall I had problems trying to get Apache to run with accept filters turned on in a jail environment... having said that, I just tried to enable it in a jail and restarted Apache and it started up fine. Maybe I was just imagining it? --Antony