Minimum Requirements to upgrade to Parallels Pro Control Panel
To upgrade to Parallels Pro Control Panel, your system needs to meet the following requirements.
Disk space At least 40 GB
/ 5 GB or more
/usr 5 GB or more
/swap Twice the size of RAM
/var 4 GB or more
20 GB or more (depending on the number of sites you want to host)
Important: Do not create /home/virtual on a separate partition. The Site Administrator dashboard reports incorrect disk usage if the directory is created on a separate partition.
Note: Sites hosted on Parallels Pro Control Panel will be accessible during the upgrade and services such as Web, FTP, and Email will continue to function, except when the site is being upgraded. However, the control panels will be inaccessible during the upgrade. This could typically range from a few minutes to a few hours depending on the number of sites hosted on the server.
Settings for ifcfg-eth0
The /etc/sysconfig/network-scripts/ifcfg-eth0 file should have the following.
—/etc/sysconfig/network-scripts/ifcfg-eth0 begin file–
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=static
IPADDR=IP_address_host_server
NETMASK=netmask_value (please check with your service provider)
GATEWAY=ip_address_gateway
—/etc/sysconfig/network-scripts/ifcfg-eth0 end file–
Before you use Parallels Pro Control Panel to perform provisioning or management operations, you must provide the license key information, if you have not provided the information at the time of installation. You receive the license key in the order confirmation email when you buy Parallels Pro Control Panel.
minimum requirements for installing Parallels Pro Control Panel
Operating system: Any of the following operating systems: FC 6 (Fedora™ Core 6), FC 4, CentOS 4.x (Community Enterprise Operating System 4.x), CentOS 5.x, RHEL 5 (Red Hat® Enterprise Linux ES Release 5), RHEL 4 ES, RHEL 4 AS.
Note: FC 4 operating system is supported only with 32-bit architecture, and all other operating systems are supported with both 32-bit and 64-bit architecture.
The system files /etc/hosts, /etc/resolv.conf, /etc/sysconfig/network, and /etc/sysconfig/network-scripts/ifcfg-eth0 on the target server must include the entries as specified below. If the entries are not present, use an editor to modify the files.
/etc/hosts file.
—/etc/hosts begin file–
127.0.0.1 localhost.localdomain localhost
1.2.3.4 myhost.mydomain.com myhost
—/etc/hosts end file–
Postfix uses database files for access control
Postfix uses database files for access control, address rewriting and other purposes.
Here is a common example of how Postfix invokes a database:
/etc/postfix/main.cf:
virtual_alias_maps = hash:/etc/postfix/virtual
Whenever you make a change to the main.cf or master.cf file, execute the following command as root in order to refresh a running mail system:
Control the MaxClients setting in Apache
A webserver should never ever have to swap, as swapping increases the latency of each request.
You can, and should, control the MaxClients* setting so that your server does not spawn so many children it starts swapping. This procedure for doing this is simple: determine the size of your average Apache process, by looking at your process list via a tool such as top, and divide this into your total available memory, leaving some room for other processes.
*MaxClients [Maximum number of connections that will be processed simultaneously]
