1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Give a user full home directory access

Discussion in 'Plesk for Linux - 8.x and Older' started by Brayden, Jun 29, 2007.

  1. Brayden

    Brayden Guest

    0
     
    Hi,

    Just wondering if anyone can help me out here.

    When a domain is created in Plesk and the user is given shell access, the home directory for that domain is /var/www/vhosts/domainName

    The user account associated with the account/domain is given write access to /var/www/vhosts/domainName/httpdocs as it is owned by them, but they are not given full access to /var/www/vhosts/domainName as it appears to be owned by "root"/

    Is there a way when creating a shell account for a user that they can be given full, complete access to /var/www/vhosts/domainName and all sub-directories to be able to edit files in there?

    Thanks in advance!

    Brayden
     
  2. raaqi

    raaqi Guest

    0
     
    anon_ftp, cgi-bin, httpdocs, httpsdocs and private should be owned by that ftp user. Not sure why everything is owned by root.

    You can always chown the directory from the SSH consol

    chown username: psaserv -R httpdocs/

    Should do the trick
     
  3. Brayden

    Brayden Guest

    0
     
    No I need to know why the "home" directory is owned by root and not the user, not the httpdocs directory. :)

    TIA,

    Brayden :)
     
  4. raaqi

    raaqi Guest

    0
     
    That's just how plesk is. If you don't like it. Just chown everything to the user under the home directory. Problem solved.
     
  5. freaky@

    freaky@ Regular Pleskian

    26
     
    Joined:
    May 2, 2006
    Messages:
    104
    Likes Received:
    0
    Perhaps it has to do with normal users not modifying vhost.conf, screwing up directory structure, removing logs, etc... Unless ofcourse you like them overriding stuff...
     
  6. Brayden

    Brayden Guest

    0
     
  7. freaky@

    freaky@ Regular Pleskian

    26
     
    Joined:
    May 2, 2006
    Messages:
    104
    Likes Received:
    0
    Sure hope you understand the risks n such...

    Those rights aren't there for nothing you know, somebody (probably more knowledgable than us) has put thought in that. For example there is a conf directory in there that will pretty much allow to override any apache/php configuration there is. They might as well use vhost.conf to configure 90 other domains and never pay for them.
     
Loading...