From owner-freebsd-apache@FreeBSD.ORG Mon Apr 20 18:29:44 2009 Return-Path: Delivered-To: apache@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5ECB7106566B for ; Mon, 20 Apr 2009 18:29:44 +0000 (UTC) (envelope-from jespasac@minibofh.org) Received: from smtp02.cdmon.com (smtp02.cdmon.com [212.36.74.229]) by mx1.freebsd.org (Postfix) with ESMTP id 2613B8FC1D for ; Mon, 20 Apr 2009 18:29:43 +0000 (UTC) (envelope-from jespasac@minibofh.org) Received: from localhost.localdomain (unknown [84.77.66.237]) by smtp02.cdmon.com (Postfix) with ESMTP id EEC0545FDC; Mon, 20 Apr 2009 20:13:14 +0200 (CEST) Message-ID: <49ECBB0A.9060606@minibofh.org> Date: Mon, 20 Apr 2009 20:12:26 +0200 From: Jordi Espasa User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: "Philip M. Gollucci" References: <49EC51F4.80603@opengea.org> <49ECB2B9.9000108@p6m7g8.com> In-Reply-To: <49ECB2B9.9000108@p6m7g8.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: apache@freebsd.org Subject: Re: About httpd 22 bug =?iso-8859-1?q?n=BA_42829?= X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2009 18:29:44 -0000 > We can add this patch, but I don't particularly like getting into the > habbit of doing this unless its something critical. Its better to lobby > upstream to make another release which includes it. I understand you position and I think your reasoning is good, but, in the other hand, you should also consider that FreeBSD is an widely used platform in production/enterprise environment. In my case (a hosting company) the present issue means a great problem: our automatizations scripts using 'apachectl graceful' a lot of times. This bug only has two possible ways: a solution or go back to 2.0.x branch. I repeat that I understand and respect your position (and work, of course!) > I have a few other tweaks to make I think and I'll bundle it with that > after the ports freeze ends. Ok. Finally I've done the following workaround: * localize the httpd-2.2.11.tar.bz2 in my /usr/ports/disfiles * untar it an localize de prefork.c file * create a http.patch file with the officinal code patch recommended and apply it in prefork.c * delete the original httpd-2.2.11.tar.bz2 * create a new httpd-2.2.11.tar.bz2 with the modified prefork.c included * recompile apache22 with portupgrade(1) using also the NO_CHEKSUM active to avoid the ports integrity checks And works fine. The nasty GGGGGGGGGGGGGGG disappear totally with this simply patch. -- Thanks, Jordi Espasa Clofent