From owner-freebsd-stable@FreeBSD.ORG Fri Feb 1 01:18:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF6E716A421; Fri, 1 Feb 2008 01:18:51 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from outbound.icp-qv1-irony-out2.iinet.net.au (outbound.icp-qv1-irony-out2.iinet.net.au [203.59.1.107]) by mx1.freebsd.org (Postfix) with ESMTP id DA14D13C447; Fri, 1 Feb 2008 01:18:50 +0000 (UTC) (envelope-from lstewart@freebsd.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CABP7oUfSVDWO/2dsb2JhbACrew X-IronPort-AV: E=Sophos;i="4.25,287,1199631600"; d="scan'208";a="272814495" Received: from unknown (HELO newbox.caia.swin.edu.au) ([210.84.53.142]) by outbound.icp-qv1-irony-out2.iinet.net.au with ESMTP; 01 Feb 2008 09:48:54 +0900 Message-ID: <47A26C76.9070306@freebsd.org> Date: Fri, 01 Feb 2008 11:48:54 +1100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.4 (X11/20070625) MIME-Version: 1.0 To: "Chris H." References: <20080131094547.54c6rsq8wgggw48s@webmail.1command.com> In-Reply-To: <20080131094547.54c6rsq8wgggw48s@webmail.1command.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: [: -le: argument expected X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2008 01:18:51 -0000 Hi Chris, Firstly, a disclaimer: I'm not an expert so I might be behind the times on what I'm about to tell you... Chris H. wrote: > Hello all, > System: > FreeBSD 7.0-PRERELEASE i386 Wed Jan 16 18:39:53 PST 2008 > > Context: > After several failed attempts to get a /stable/ installation of > Apache13-ssl > and friends built and installed from source (see thread: > /usr/bin/objformat, for > more background). I chose to look at the possibility of using Apache > 2.0. I was > reluctant, as doing so would require migrating ~50 carefully crafted > conf files > which have evolved over many yrs. to be now seemingly impervious to > abuse, or > attack. I hadn't intended this server to become a guinea pig, but my ill > fated > attempts to install a stable copy of www/apache13-ssl from source > necessitated > increasing the resources on the other servers. So as to experiment on > this one. > > To the point! > Building Apache 2.0 on this box requied cvsupping src/ports (2008-01-30). > As the version of Apache 2.0 was 2.0.61 (has 2 security related issues). > Current version: > 2.0.63. Building/installing this version went w/o trouble. Ran as expected. > I only made 1 mod from the default config/build: WITH_MPM?= threadpool. > The original was: WITH_MPM?= prefork. My diong so also required: KQUEUE. > Other than that, all was as-was. > [snip] Regardless of the errors you reported, I believe changing the MPM is a problem. Last time I tried Apache with the threaded worker MPM it worked flawlessly. However PHP has issues because it isn't thread safe. The only safe way to run the 2 together was to set the Apache MPM back to the default (prefork). Taking my disclaimer into account, I possibly just didn't figure out how to make the 2 play nice, so I'd welcome info/pointers from others who have managed to get threaded apache and PHP working together. Assuming no one pipes up and explains how to work around the PHP threading issues, I'd recommend rebuilding apache with the default MPM (shouldn't require any make variables defined). Verify it works ok once installed and then try get PHP working again. I would also echo the recommendation of others to jump straight to Apache 2.2(.8) if you're going to make a disruptive switch now anyways. I have a personal step-by-step build guide for getting Apache 2.2 and PHP5 working together if you're interested. As to your reported errors, I can't really shed any light on them, sorry. Cheers, Lawrence