Date: Thu, 14 Feb 2008 19:30:37 +0300 From: Stanislav Sedov <stas@FreeBSD.org> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-performance@freebsd.org, Antony Mawer <fbsd-performance@mawer.org>, Alexey Popov <lol@chistydom.ru> Subject: Re: PHP with open_basedir performance problem Message-ID: <20080214163037.GA51014@dracon.ht-systems.ru> In-Reply-To: <479DE578.7060202@quip.cz> References: <479B1185.8020604@quip.cz> <479D89C9.7060300@chistydom.ru> <479DD94C.7010409@mawer.org> <479DE578.7060202@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080214163037.GA51014>