Results 1 to 5 of 5

Thread: Permissions CHOWN vs CHMOD

  1. #1
    marcroth is offline Junior Member
    Join Date
    Feb 2006
    Posts
    4

    Question Permissions CHOWN vs CHMOD

    Hi there,

    I am quite a beginner with Sugar. Anyway, I have constant issues with upgrading and installing my sugar. I understand it's because of the directory persmissions - if I CHMOD everything to 777 no problem!

    However, I think this is not secure, thus I prefer only to give owner and/or group permissions! Though, I don't have the right to CHOWN on the server I host (its shared and I don't even have shell access), but they give me a fix the group name and the owner name is automatically defined when I upload with FTP.

    My question: How/where in the Sugar Setting can I change the owner/group names that Suger uses to access the server when running the various phps.

    Thanks a lot!
    Marc

  2. #2
    stevec is offline Sugar Community Member
    Join Date
    Oct 2005
    Location
    London
    Posts
    1,100

    Default Re: Permissions CHOWN vs CHMOD

    Hi,

    The php scripts are run by the user and it's group set in the apache config - there is no specific user for sugar. For my machine, it's the 'www-data' user and group - as this is the user the apache web server runs under for Debian/Ubuntu

  3. #3
    marcroth is offline Junior Member
    Join Date
    Feb 2006
    Posts
    4

    Default Re: Permissions CHOWN vs CHMOD

    Okay, but why the routines executed by sugar don't work if I only CHMOD 774 (instead of 777), meaning that I dont' give the public access to writing and execution? It seems everything executed by sugar is not considered under my group/owner login, but as public. How can I change this`?

    Thanks! Marc

  4. #4
    kushalk is offline Sugar Community Member
    Join Date
    Feb 2006
    Posts
    12

    Default Re: Permissions CHOWN vs CHMOD

    Quote Originally Posted by marcroth
    Okay, but why the routines executed by sugar don't work if I only CHMOD 774 (instead of 777), meaning that I dont' give the public access to writing and execution? It seems everything executed by sugar is not considered under my group/owner login, but as public. How can I change this`?

    Thanks! Marc
    Actually in Unix like machines 774 permission of a directory means owner and group have all the permissions but other has only read permission. And webserver user apache (in Red had Linux ) will fall in the others, so it was not able to install the Sugar.

    Ask your hosting provider to add webserver user (apache or nobody whichever is the case) into the group of the Sugar folder.

  5. #5
    m2farzana is offline Junior Member
    Join Date
    Oct 2007
    Posts
    3

    Default Re: Permissions CHOWN vs CHMOD

    I installed sugarcrm but after login as admin I found no dashlet information in my Home module and if I create any lead that doesn’t display anymore…
    MY webserver’s OS is linux,php version 5.1.6 and Mysql 5.2
    I changed the cache,custom,data and module property to 777 as recommened in sugar wiki.But after installing sugar I found in cache directory some new directory was created …
    The newly created directory property is still 755
    For example,
    During installation Cache directory created new directory dashlets but its property is 755…..it should be 777 by default and its files default property should be 666.

    I ftp sugarcrm files with user crm/apache(owner/group) but newly created directory owner/group is apache/apache.
    I had installed sugarcrm in another linux machine and it worked properly
    My question is why new directory own by apache but in other server its own by non apache user. How can we make it so that ftp user owns the new directory


    Please help ...I am stuck with this...

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •