<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 00:08:20 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Rob Thompson's Blog: PHP and Solaris - getcwd() Behavior]]></title>
      <guid>http://www.phpdeveloper.org/news/9022</guid>
      <link>http://www.phpdeveloper.org/news/9022</link>
      <description><![CDATA[<p>
<i>Rob Thompson</i> <a href="http://rob.sun3.org/php-code/php-and-solaris-getcwd-behavior/">passed along</a> 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.
</p>
<blockquote>
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.
</blockquote>
<p>
He does note, happily, that this issue is <a href="http://rob.sun3.org/php-code/php-and-solaris-getcwd-behavior/">cleared up with an upgrade</a> 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.
</p>]]></description>
      <pubDate>Mon, 12 Nov 2007 13:47:00 -0600</pubDate>
    </item>
  </channel>
</rss>
