Summary | chmod in gollem is very confusing |
Queue | Horde Framework Packages |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | jan (at) horde (dot) org |
Requester | michael (at) bigmichi1 (dot) de |
Created | 10/11/2011 (5013 days ago) |
Due | |
Updated | 10/11/2011 (5013 days ago) |
Assigned | |
Resolved | 10/11/2011 (5013 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
Queue ⇒ Horde Framework Packages
Fix setting permissions with File driver (
Bug #10630).The permissions are passed as strings in octal notation, but chmod()
expects an
integer.
2 files changed, 6 insertions(+), 4 deletions(-)
http://git.horde.org/horde-git/-/commit/b0fde9ef389171d1871c1c7ee1a565f04e18abd3
Permissions != umask (
Bug #10630).1 files changed, 1 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/c312c97f80eef5688ffba89743cd6cda3ff57cad
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ chmod in gollem is very confusing
Queue ⇒ Gollem
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
only read for user the result is:-rw--w----
only read and write for user the result is:---x-wx--T
read and write for user and read for group the result is: --w------T
my umask setting for the backend is set to 077 in horde config and
included in backends.local.php as:
$backends['file']['params']['permissions'] = $GLOBALS['conf']['umask'];