ZF-320: hashedDirectoryUmask wont work on some installations

Issue Type:
Bug
Created:
2006-08-15T06:11:36.000+0000
Last Updated:
2012-02-22T22:41:14.000+0000
Status:
Resolved
Fix version(s):
  • 0.2.0 (29/Oct/06)
Reporter:
Marco Kaiser (bate)
Assignee:
Fabien MARTY (fab)
Tags:
  • Zend_Cache
Related issues:
Attachments:

Description

On some installations this would make the directory with the specific dirmask @mkdir($this->_path(self::_idToFileName($id)), $this->_options['hashedDirectoryUmask'], true);

because mkdir relays on the umask settings.

Solution: umask(000) before or a single chmod after this.

Comments

Posted by Fabien MARTY (fab) on 2006-08-23T15:34:18.000+0000

do you say that we have to replace the line :

@mkdir($this->_path(self::_idToFileName($id)), $this->_options['hashedDirectoryUmask'], true);

by :

@mkdir($this->_path(self::_idToFileName($id)), $this->_options['hashedDirectoryUmask'], true); @chmod($this->_options['hashedDirectoryUmask']);

?

Posted by Marco Kaiser (bate) on 2006-08-23T15:39:27.000+0000

Maybe, the 2nd argument to mkdir relays on the umask and chmod not. But yes, your solution should work. :)