#18908 [Com]: Not getting Current Working Directory

From: Date: Fri, 06 Sep 2002 19:18:48 +0000
Subject: #18908 [Com]: Not getting Current Working Directory
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-18587@lists.php.net to get a copy of this message
ID: 18908 Comment by: duke@mastre.com Reported By: duke@mastre.com Status: Closed Bug Type: Apache2 related Operating System: Linux 2.4.19 PHP Version: 4CVS-2002-08-14 New Comment: So PHP 4.2.3 came out today. I am still experiencing this very same problem - PHP can't get the current working directory under Apache 2[.0.40]. It only seems to work with the unstable snapshot du jour. Previous Comments: ------------------------------------------------------------------------ [2002-08-15 11:02:53] duke@mastre.com . ------------------------------------------------------------------------ [2002-08-15 11:00:29] duke@mastre.com I tried with the unstable snapshot and it works. ------------------------------------------------------------------------ [2002-08-14 22:28:14] kalowsky@php.net moving this to apache2 related. Please realize that PHP and Apache2 is a VERY experiemental thing, and not very likely to be fixed quickly. And yes we developers are reading this... ------------------------------------------------------------------------ [2002-08-14 22:19:27] duke@mastre.com I'm sure it will work, my problem is on Apache2. If I didn't need to run with Apache2 I wouldn't be using the snapshot in the first place. I would be interested to know if you can duplicate it on FreeBSD/OS X using Apache2. Any developer out there reading this? ------------------------------------------------------------------------ [2002-08-14 19:17:03] kalowsky@php.net Running on FreeBSD, and MacOSX I cannot reproduce this problem.. I get the following output: current working directory: /Users/dank/Development/php4-cvs<br /> w/o getcwd(): true<br /> with getcwd() . /: true This is from CVS HEAD. I'm also not using Apache2 though. Any chance you can try this with Apache 1.3.x? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/18908 -- Edit this bug report at http://bugs.php.net/?id=18908&edit=1

« previous php.bugs (#18587) next »