PHPDeveloper.org http://www.phpdeveloper.org Up-to-the Minute PHP News, views and community en-us Tue, 18 Jun 2013 23:43:57 -0500 30 <![CDATA[Rob Thompson's Blog: PHP and Solaris - getcwd() Behavior]]> http://www.phpdeveloper.org/news/9022 http://www.phpdeveloper.org/news/9022 Rob Thompson passed along some information that PHP users running on Solaris might want to check out - the slightly buggy behavior of the PHP getcwd function on the platform.

Many functions within the PHP codebase relied upon a universally working getcwd() [C] call to expand paths and to find out where a script is being executed. In particular, Solaris does not assume that getcwd() is a privilege that should be granted to users in directories that don't have 'r' (read) permission, even if it has 'x' (execute) permissions. [...] Under Linux, getcwd() behaves normally but under Solaris, getcwd() does not work with the --x restrictive permissions.

He does note, happily, that this issue is cleared up with an upgrade to PHP 5.2.5 as soon as possible. He had code snippets included in the post so you can test your installation for the problem too.

]]> Mon, 12 Nov 2007 13:47:00 -0600 <![CDATA[IBM developerWorks Blog: What's the problem? (Working Directories)]]> http://www.phpdeveloper.org/news/5382 http://www.phpdeveloper.org/news/5382 On the IBM developerWorks blog today, there's this look at the differences between PHP and Windows when it comes to the working directory you're grabbing in your script.

I recently investigated the values of the PHP and Windows working directory for a variety of environments. My reason for doing so was that I could never quite understand how relative pathnames were resolved, and if you want to write code that will run, for example, both under Zend Studio, from the command line, and Apache, it matters. And it is not surprising that I never understood it either - every environment is different.

He ran five tests to show each of the environments that a PHP script might be running in and what two methods return - PHP's getcwd and Windows' getcwd in direct.h). There are some similarities between the output of the two, but there's enough difference to be worrysome for any programmer making scripts for both. He also gives a specific example of a situation he was in involving incorrect paths and libxml2 and the difficulties that were found there.

]]> Wed, 17 May 2006 05:59:28 -0500