Description: ------------ If for some reason the Registry::install_dir does not exist and the user (webserver) has no write-access to any part of that path, Registry::hasWriteAccess will loop endless. function hasWriteAccess() { if (!file_exists($this->install_dir)) { $dir = $this->install_dir; while ($dir && $dir != '.') { $dir = dirname($dir); // cd .. if ($dir != '.' && file_exists($dir)) { if (is_writeable($dir)) { return true; } else { return false; } } if ($dir == '/') break; } return false; } return is_writeable($this->install_dir); } As dirname($dir='/') returns again '/'. The fix shown above, breaks that endless loop. Ralf

Hold on - the code should exit because file_exists('/') is true. Could you verify the output of this script: <?php var_dump(file_exists('/')); ?> is bool(true) I can't reproduce the behavior you describe in any circumstance. Perhaps there is some critical piece of information missing? What path was install_dir? Which directories exist?

aha - you have safe_mode active, don't you? file_exists() would return false on / in this case.

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.

Hi, the site is NOT using safe_mode, only open_basedir, which only includes the docroot and the pear directory. As a workaround I check now in our installer if the install-dir exists and fallback on our old mode of checking a pear package is available by trying to include it. Unfortunately this does not give the version numbers, I need for dependency checks. But calling the pear registry goes in that endless loop. You can have a look at the code at: http://www.egroupware.org/viewvc/trunk/setup/check_install.php?revision=24107&view=markup search for get_installed_pear_packages() I'm not considering this problem fixed, as I have no influence on the wrong configuration. I personally think it's a bug, that this misconfiguration causes the pear registry class to go in an endless loop. Please re-consider your decision not to fix it and to close this bug. Thanks for your help anyway :-) Ralf

?? Closed = fixed Bogus = not a bug. This has been fixed in cvs http://cvs.php.net/viewvc.cgi/pear-core/PEAR/Registry.php?r1=1.165&r2=1.166