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

Partition Recommendations

Discussion in 'Plesk for Linux - 8.x and Older' started by chrisl@, Oct 26, 2005.

  1. chrisl@

    chrisl@ Guest


    Wondering if anyone has partition recommendations for a Fedora install. Really what I am looking for is where the bulk of the data for plesk will be. What is the directory structure for user content webroot, db, etc so I can make this the largest partition. I have not done a plesk install before so looking for suggestions.

  2. ShadowMan@

    ShadowMan@ Guest

    With Plesk 7.5.3 and earlier it defaults to using


    With 7.5.4 on fresh OS (newer distros) it defaults to


    Upgrades to 7.5.4 usually will be the /home/httpd/vhosts/....
  3. chrisl@

    chrisl@ Guest

    thanks that is what I needed, this is a totally fresh install.
  4. dahamsta

    dahamsta Guest

    Didn't know that. Was there a particular reason for changing do we know?
  5. ShadowMan@

    ShadowMan@ Guest

    There was a heated post some weeks ago about this issue. It comes down to Plesk adhering to FHS = Filesystem Hierarchy Standard

    Regardless, you can change the vhost path in /etc/psa/psa.conf:

    # Virtual hosts directory
    HTTPD_VHOSTS_D /home/httpd/vhosts

    for new OS installs if you don't want to have it in /var/www/vhosts.

    For more on this topic, see pages 4,5, 6 at

    http://forum.plesk.com/showthread.p...perpage=15&highlight=file system&pagenumber=4

    As to recommendations for partitions:

    I and many people just do:

    /tmp (optional)

    where '/' is the largest amount possible, /boot is the smallest for the distro needs

    /tmp being separate is always in debate, making it no exec is one thing, but not really a strong protection for the server. Kernel hardening and other methods/configs will do you much better.