• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

var, bin, usr, etc, lib, and tmp directories created in vhosts/domain

G

ganast

Guest
I just moved a bunch of domains from one server (PLESK 7.5.1/RH7.3) to another server (PLESK 7.5.4/RHEL3) using the migration manager.

Almost every domain has var, bin, usr, etc, lib, and tmp directories in addition to the usual anon_ftp, cgi-bin, conf, etc directories.

e.g.:
#ls /var/www/vhosts/domain.com
anon_ftp cgi-bin error_docs httpdocs lib private subdomains usr web_users bin conf etc httpsdocs pd statistics tmp var


Is this supposed to be like this, or should I delete all these "root-alikes?" Where did they come from anyway?

--gabe
 
That's how it's supposed to be. If you wish to hide these 'system' files, edit the proftpd.conf file. Look for:

<Directory /var/www/vhosts>
GroupOwner psacln
</Directory>

And change it to:

<Directory /var/www/vhosts>
GroupOwner psacln
HideNoAccess On
HideUser root
</Directory>

The only problem I have found is that if you chmod a directory in the cgi-bin so that it's not executable, the folder is then hidden.
 
Huh, I don't really care actually, just didn't want to opern any security holes.

Can I use this directories? I would actually use the usr directory in most of my domains if I knew that it was going to become a permanent fixture in PLESK...

What are the directories for? for things like php safe-mode?

--gabe
 
I just found this post. Was there ever an answer to the last question. I would like to see it if there was.
 
Never got any kind of answer, but maybe I will expand my question.

On many of my domains I use TYPO3.

Ususally I make a typo3-src directory in the domain.com directory, I then change the conf/vhost.conf file to modify open-basedir access to that typo3-src directory outside of the httpdocs webroot.

The problem is that when I move one of these domains to a new server, the migration utility ignores the typo3-src directory and I have to move it by hand.

I thought that if the usr directory gets moved via migration utility (I could check this, just have not as of yet) then I would move my typo3-src directory into usr/share/typo3

anyone?

--gabe
 
Back
Top