Clarification of default_permissions

[seade]

config.php defines default_permissions which as far as I understand it should control the file ownership and permissions on Linux.

If possible I would like to be able to have the files owned by my user rather than apache so I have this:

   'default_permissions' =>
  array (
    'dir_mode' => 1528,
    'file_mode' => 432,
    'user' => 'myuser',
    'group' => 'apache',
  ), 
  

With the above setting I would expect any new files and directories to be owned by my user but with apache being able to write files. It seems however that this is not the case. If I attempt to upgrade my 5.1CE to 5.1aCE I get:

Specified directory '' for zip file '/home/myuser/public_html/sugarcrm/cache/upload/SugarCE-Patch-5.1.0a.zip' extraction does not exist.

and if list the files in the upload directory:

-rw------- 1 apache apache 1593257 Oct  7 13:23 cache/upload/SugarCE-Patch-5.1.0a.zip

See how the owner is still apache and the group does not have rw.

So I guess default_permissions doesn't work the way I imagined it might. Is there a way to get this working or will I just have do go back to having the files owned by apache?

Thanks,

Scott

[seade]

Does anyone know how this is supposed to work?

[roblaus]

The above mentioned permissions don't have anything to do with it. There was a bug in 5 (or 5.1RC - not sure) that caused this error. But this should have been fixed already. PLease make sure that you really upgrade from 5.1GA to 5.1a.
If this is the case I am afraid I have no clue. You may also search the forum for this exact error.

[seade]

If possible I would like to be able to have the files owned by my user rather than apache so I have this:

   'default_permissions' =>
  array (
    'dir_mode' => 1528,
    'file_mode' => 432,
    'user' => 'myuser',
    'group' => 'apache',
  ), 
  

The above was actually the source of the error for me. I had

   'default_permissions' =>
  array (
    'dir_mode' => 1528,
    'file_mode' => 432,
    'user' => 'apache',
    'group' => 'users',
  ), 
  

but of course the user apache is not allowed to chgrp to the users group. I am now running with this:

   'default_permissions' =>
  array (
    'dir_mode' => 1528,
    'file_mode' => 432,
    'user' => 'apache',
    'group' => 'apache',
  ), 
  

and can upgrade my system. The error message was totally useless. What was actually happening was that sugar was attempting to create a temporary directory. When it did so it was attempting to chgrp to the users group and this operation failed. Instead of outputting something useful the relevant function simply returns false and the net result is that the path becomes the empty string that appears in the error message.

So what is the point of these configuration parameters when most web servers are locked down in this way.

They don't seem to make any difference and we still need sudo access to access any files that are created by sugar.

Scott