From owner-freebsd-performance@FreeBSD.ORG Thu Feb 14 16:56:28 2008 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA46416A46C for ; Thu, 14 Feb 2008 16:56:28 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from smtp.ht-systems.ru (mr0.ht-systems.ru [78.110.50.55]) by mx1.freebsd.org (Postfix) with ESMTP id 8490013C461 for ; Thu, 14 Feb 2008 16:56:28 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from [78.110.49.49] (helo=quasar.ht-systems.ru) by smtp.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1JPgys-0000DK-Iq; Thu, 14 Feb 2008 19:30:38 +0300 Received: by quasar.ht-systems.ru (Postfix, from userid 1024) id 703267D1002; Thu, 14 Feb 2008 19:30:37 +0300 (MSK) Date: Thu, 14 Feb 2008 19:30:37 +0300 From: Stanislav Sedov To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20080214163037.GA51014@dracon.ht-systems.ru> References: <479B1185.8020604@quip.cz> <479D89C9.7060300@chistydom.ru> <479DD94C.7010409@mawer.org> <479DE578.7060202@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <479DE578.7060202@quip.cz> Organization: The FreeBSD Project X-Voice: +7 916 849 20 23 X-XMPP: ssedov@jabber.ru X-Yahoo: stanislav_sedov X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-University: MEPhI X-Mailer: carrier-pigeon X-Operating-System: FreeBSD quasar.ht-systems.ru 7.0-BETA2 FreeBSD 7.0-BETA2 Cc: freebsd-performance@freebsd.org, Antony Mawer , Alexey Popov Subject: Re: PHP with open_basedir performance problem X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2008 16:56:28 -0000 On Mon, Jan 28, 2008 at 03:23:52PM +0100 Miroslav Lachman mentioned: > > Does somebody have any other ideas? > I'd suggest you to disable open_basedir at all or roll out specialized implementation. I had a lot of similar problems with open_basedir in the past, so I just rewrote it to match our specific security policy. Most basedir problems are linked with the fact it produce a lot of lstast/ readlinks on every require, include or open command. On Linux it pereforms even worse, as they implemented readlink there by hand, and, of course, their implementation isn't particulry good. I don't thinks this problem could be solved with PHP guys, taking in account the fact that a simple bug report with the patch usually result in two weeks of formal replies like "it's not a bug, it's a feature". Not speaking about they desicover new bugs in basedir every couple of days. -- Stanislav Sedov ST4096-RIPE