Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50113
Return-Path: <frozenfire@thefrozenfire.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 43658 invoked from network); 6 Nov 2010 20:37:58 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 6 Nov 2010 20:37:58 -0000
X-Host-Fingerprint: 173.180.120.12 unknown  
Received: from [173.180.120.12] ([173.180.120.12:29101] helo=localhost.localdomain)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 9B/48-19689-5ACB5DC4 for <internals@lists.php.net>; Sat, 06 Nov 2010 15:37:57 -0500
Message-ID: <9B.48.19689.5ACB5DC4@pb1.pair.com>
To: internals@lists.php.net
Date: Sat, 06 Nov 2010 13:37:54 -0700
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Posted-By: 173.180.120.12
Subject: chroot function availability disqualifiers
From: frozenfire@thefrozenfire.com (Justin Martin)

Hello everyone,

As a bit of proactive documentation, I'm trying to determine exactly 
what the disqualifying conditions are for chroot's availability in PHP.

So far as I can tell, from ext/standard/dir.c, chroot is only compiled 
in #if defined(HAVE_CHROOT) && !defined(ZTS) && ENABLE_CHROOT_FUNC

HAVE_CHROOT seems to always be set to 1 by php_config.h, so far as I can 
tell. ZTS, as I understand it, indicates whether PHP is being compiled 
threadsafe, and ENABLE_CHROOT_FUNC seems to be related to the 
deprecated(?) --enable-chroot-func switch.

Could someone with a better understanding of the compile process 
illuminate me as to all of the reasons why chroot might not be available?

Thanks,
Justin Martin, a.k.a. FrozenFire